On the consolidated database, create a new script version for your file-based download and implement any scripts required by your existing synchronization system into it. Upload scripts are not required. This script version is used only for file-based download. For this script version, all scripts that take MobiLink user names as parameters, instead, take a MobiLink user name that refers to a group of remote databases. This is the user name that is defined in the file-definition database.
For each script version that you have defined, implement a begin_publication script.
For timestamp-based downloads, implement a modify_last_download_timestamp script for each script version. How you implement this script depends on how much data you intend to send in each download file. For example, one approach is to use the earliest time that any user from the group last downloaded successfully. Remember that the ml_username parameter passed to this script is actually the group name.
It is strongly recommend that you use the -dsd option on the MobiLink server when generating file-based download files from
a Microsoft SQL Server consolidated database. If you do not use the -dsd option, remotes may occasionally be unable to apply
a file-based download file and will report an error similar to the following:
The last download time for publication <publication> is <timestamp> The download file's next last download time was <timestamp>
Cannot apply a download file if its next last download time is before the publication's last download time.
Generally, the frequency with which a remote database is unable to apply a download file will be proportional to the frequency with which the remote database performs normal (connected) synchronizations and the amount of concurrent activity in the consolidated database.
See -dsd mlsrv12 option.
Discuss this page in DocCommentXchange.
|Copyright © 2012, iAnywhere Solutions, Inc. - SQL Anywhere 12.0.1|