On SQL Anywhere clients, an attempt is made to execute any waiting scripts at the end of each synchronization. The available scripts are ordered by run_order and executed one at a time until one of the following occurs:
A script cannot be executed automatically if any of the following are true:
Download-only publications should never be listed as affected publications.
At the beginning of a synchronization, dbmlsync may choose to obtain locks on the synchronizing tables that are more restrictive than those requested using the LockTables extended option in order to ensure that scripts can be executed at the end of the synchronization. For example, if LockTables is set to SHARE but the next script available for execution requires exclusive locks, then exclusive locks may be obtained.
|Send feedback about this page via email or DocCommentXchange||Copyright © 2008, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.0|