SQL Remote behavior changes and deprecated features

This topic has been updated for build 1823.

As with all forward-looking statements, the lists of deprecated features are not guaranteed to be complete and are subject to change.

Following is a list of changes to SQL Remote introduced in version 16.0.

dbremote offline transaction log retrieval has changed The dbremote utility can now retrieve offline transaction logs from the SQL Anywhere database server instead of accessing them directly. If offline transaction logs are required but the given offline transaction log directory cannot be opened or it does not contain offline transaction log files, then dbremote retrieves the offline transaction logs through the database server. The following restrictions apply:
- The user ID that is used by dbremote to connect to the synchronization database must have the READ FILE and WRITE FILE privileges and all the offline transaction log files must be in the online transaction log directory.
- The database server must have Support Package build number 1823 or later to support this feature.
There is a slight performance penalty when using this feature because the database server must do extra work to retrieve the transaction logs.

Discuss this page in DocCommentXchange.