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 download it again by defining a modify_last_download_timestamp connection script to reset the value for the last download timestamp. There are other events, called generate_next_last_download_timestamp and modify_next_last_download_timestamp, which you can use to set the timestamp not for the current synchronization but for the next synchronization. For example, if you wanted to use a UTC timestamp value to compare to UTC values in the last_modified columns of your tables. See:

• modify_last_download_timestamp connection event
• generate_next_last_download_timestamp event
• modify_next_last_download_timestamp connection event

UltraLite also provides functionality to change the last download time from the remote. See:

• C/C++ embedded SQL: ULResetLastDownloadTime method
• C++: ResetLastDownloadTime method
• .NET: ResetLastDownloadTime method

• Using last download times in scripts