Instead of running dbmlsync in a batch fashion, where it synchronizes and then shuts down, you can set up a SQL Anywhere client so that dbmlsync runs continuously, synchronizing at predetermined times.
You specify the synchronization schedule as an extended option. It can be specified either on the dbmlsync command line or it can be stored in the database for the synchronization user, subscription, or publication.
This method is not available when the Dbmlsync API or the SQL SYNCHRONIZE statement is used.
Add scheduling to the synchronization subscription Set the Schedule extended option in the synchronization subscription. For example:
CREATE SYNCHRONIZATION SUBSCRIPTION TO mypub FOR mluser ADDRESS 'host=localhost' OPTION schedule='weekday@11:30am-12:30pm' |
You can override scheduling and synchronize immediately using the dbmlsync -is option. The -is option instructs dbmlsync to ignore scheduling that is specified with the scheduling extended option.
Add scheduling from the dbmlsync command line Set the schedule extended option. Extended options are set with -e or -eu. For example:
dbmlsync -e "sch=weekday@11:30am-12:30pm" ... |
If scheduled synchronization is specified in either place, dbmlsync does not shut down after synchronizing, but runs continuously.
See also |
Discuss this page in DocCommentXchange.
|
Copyright © 2014, SAP AG or an SAP affiliate company. - SAP Sybase SQL Anywhere 16.0 |