sp_hook_dbmlsync_download_sql

sp_hook_dbmlsync_download_sql_error (deprecated)

Handle database errors that occur while applying the download sent by the MobiLink server.

This hook is deprecated. See Handling errors and warnings in event hook procedures.

Rows in #hook_dict table

Name	Value	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.
continue (in\|out)	true \| false	Indicates whether the error should be ignored and synchronization should continue. This parameter should be set to false to call the sp_hook_dbmlsync_download_fatal_sql_error hook and stop synchronization. If you set this parameter to true, dbmlsync ignores the error and continues with synchronization, which may result in data loss.
SQL error code (in)	SQL error code	Identifies the SQL error code returned by the database when the operation failed.
publication_n (in)	publication	The publications being synchronized, where n is an integer. There is one publication_n entry for each publication being uploaded. The numbering of n starts at zero.
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.

Remarks

If a procedure of this name exists, it is invoked when a database error is detected during the download phase of synchronization. The procedure is only invoked for errors where it is possible to ignore the error and continue with synchronization. For fatal errors, the sp_hook_dbmlsync_download_fatal_SQL_error procedure is called.

Caution

When continue is set to TRUE, dbmlsync simply ignores the database error and continues with synchronization. There is no attempt to retry the operation that failed. As a result, some or all of the download may be lost. The amount of data lost depends on the type of error encountered, when it occurred, and what steps the hook took to recover. It is very difficult to predict which data is lost and so this feature must be used with extreme caution. Most users would be best advised to not attempt to continue after a SQL error.

Actions of this procedure are committed or rolled back when the download is committed or rolled back.