MobiLink generates and uses a timestamp for timestamp-based downloads as follows:
The last download time is stored on the remote database. This is the appropriate place because only the remote knows if the download has been successfully applied.
For SQL Anywhere remotes, the last download time is stored per subscription. See SYSSYNC system view.
For UltraLite remotes, the last download time is stored per publication. See syspublication system table.
In some rare circumstances you may want to modify the last_download_timestamp. For example, if you accidentally delete all the data on a remote database, you can resynchronize it by defining a modify_last_download_timestamp connection script to reset the value for the last download timestamp. There is another event, called modify_next_last_download_timestamp, which you can use to reset the timestamp not for the current synchronization but for the next synchronization. See:
UltraLite also provides functionality to change the last download time from the remote. See:
|Send feedback about this page via email or DocCommentXchange||Copyright © 2008, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.0|