Extended options can be specified on the dbmlsync command line using the -e or -eu options, or they can be stored in the database. You store extended options in the database by using Sybase Central, by using the sp_hook_dbmlsync_set_extended_options event hook, or by using the OPTION clause in any of the following statements:
CREATE SYNCHRONIZATION SUBSCRIPTION
ALTER SYNCHRONIZATION SUBSCRIPTION
CREATE SYNCHRONIZATION USER
ALTER SYNCHRONIZATION USER
CREATE SYNCHRONIZATION SUBSCRIPTION without specifying a synchronization user (which associates extended options with a publication)
Dbmlsync combines options stored in the database with those specified on the command line. If conflicting options are specified, dbmlsync resolves them as follows. In the following list, options specified by methods occurring earlier in the list take precedence over those occurring later in the list.
Options specified in the sp_hook_dbmlsync_set_extended_options event hook.
Options specified in the command line that aren't extended options. (For example,
Options specified on the command line with the -eu option.
Options specified on the command line with the -e option.
Options specified for the subscription, whether by a SQL statement or in Sybase Central. When you use the Deploy Synchronization Model wizard to deploy a MobiLink model, extended options are set for you and are specified in the subscription.
Options specified for the MobiLink user, whether by a SQL statement or in Sybase Central.
Options specified for the publication, whether by a SQL statement or in Sybase Central.
This priority order also affects connection parameters, such as those specified with the TYPE and ADDRESS options in the SQL statements mentioned above.
You can review extended options in the log and the SYSSYNC system view.
For information on how extended options can be used to tune synchronization, see Using dbmlsync extended options.
The following dbmlsync command line illustrates how you can set extended options when you start dbmlsync:
dbmlsync -e "adr=host=localhost;dir=c:\db\logs"...
The following SQL statement illustrates how you can store extended options in the database:
CREATE SYNCHRONIZATION SUBSCRIPTION TO mypub FOR mluser ADDRESS 'host=localhost' OPTION schedule='weekday@11:30am-12:30pm', dir='c:\db\logs'
The following dbmlsync command line opens the usage screen that lists options and their syntax: