Like the upload, the download starts and ends with connection events. Other events are table-level events.

The begin_download and end_download scripts for each remote table hold logic that is independent of the individual rows being updated.

The download does not distinguish between inserts and updates. The script associated with the download_cursor event is a SELECT statement that defines the rows to be downloaded. The client detects whether the row exists or not and then it performs the appropriate insert or update operation.

For timestamp-based downloads, you specify the last_table_download parameter to ensure that only changes since the last synchronization are downloaded. For example, the download_cursor or download_delete_cursor SQL script could include the line:

WHERE Customer.last_modified >= {ml s.last_table_download}

See Using last download times in scripts.

At the end of the download processing, the client automatically deletes rows if necessary to avoid referential integrity violations.

If you change the SendDownloadAck setting to ON, the download transaction is committed but the acknowledgement scripts are not executed until the acknowledgement is received.

By default, SendDownloadAck is set to OFF.

See SendDownloadAck (sa) extended option, Send Download Acknowledgement synchronization parameter, nonblocking_download_ack connection event and publication_nonblocking_download_ack connection event.