Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 11.0.1 » MobiLink - Client Administration » SQL Anywhere Clients for MobiLink » Event hooks for SQL Anywhere clients » Introduction to dbmlsync hooks » Using event-hook procedures


Connections for event-hook procedures

Each event-hook procedure is executed on the same connection as the synchronization itself. The following are exceptions:

  • sp_hook_dbmlsync_all_error

  • sp_hook_dbmlsync_communication_error

  • sp_hook_dbmlsync_download_com_error

  • sp_hook_dbmlsync_download_fatal_sql_error

  • sp_hook_dbmlsync_download_log_ri_violation

  • sp_hook_dbmlsync_misc_error

  • sp_hook_dbmlsync_sql_error

These procedures are called before a synchronization fails. On failure, synchronization actions are rolled back. By executing on a separate connection, you can use these procedures to log information about the failure, without the logging actions being rolled back along with the synchronization actions.