MobiLink Synchronization Reference
Stored Procedures
Client event-hook procedures
Take action when a synchronization download is about to be rolled back because of a database error.
| Name | Values | Description |
|---|---|---|
| table name (in) | table name | The table to which operations were being applied when the error occurred. The value is an empty string if dbmlsync is unable to identify the table. |
| SQL error code (in) | SQL error code | Identifies the SQL error code returned by the database when the operation failed. |
| publication_n (in) | publication name | The publications being synchronized, where n is an integer. There is one publication_n entry for each publication being uploaded. |
| MobiLink user (in) | MobiLink user name | The MobiLink user for which you are synchronizing. |
| script version (in) | script version name | The MobiLink script version to be used for the synchronization. |
If a procedure of this name exists, it is called immediately before a synchronization download is rolled back because of a database error. This occurs whenever an SQL error is encountered that cannot be ignored, or when the sp_hook_dbmlsync_download_SQL_error hook has already been called and has chosen not to ignore the error.
This procedure executes on a separate connection, so that failures can be logged. Otherwise, the action of logging would be rolled back along with the synchronization actions. If dbmlsync cannot establish a separate connection, the procedure is not called.
By default on Windows CE devices, synchronization tables are locked in exclusive mode, which means that this hook cannot successfully execute if it requires access to any of the synchronization tables. It also cannot execute if it needs to access synchronization tables and you set the dbmlsync extended option LockTables to EXCLUSIVE. For more information, see LockTables (lt) extended option.
Actions of this procedure are committed immediately after execution.
Synchronization event hook sequence
sp_hook_dbmlsync_download_sql_error