It is recommended that you use the Extraction utility (dbxtract) or the Extract Database Wizard to synchronize subscriptions. See Synchronize.
Extracting a large number of subscriptions, or synchronizing subscriptions to large, frequently-used tables, can slow database access. You can use the SEND AT clause to specify a time to synchronize when the consolidated database is not in heavy use. See Setting the send frequency.
Connect to the consolidated database as a user with DBA authority.
Execute a SYNCHRONIZE SUBSCRIPTION statement. See SYNCHRONIZE SUBSCRIPTION statement [SQL Remote].
The Message Agent (dbremote) on the consolidated database sends a copy of all rows in the subscription to the subscriber. The Message Agent (dbremote) assumes that an appropriate database schema is in place at the remote databases.
The Message Agent (dbremote) on the subscriber database receives the synchronization message and it replaces the current contents of the subscribed tables with the new copy.
Do not execute a SYNCHRONIZE SUBSCRIPTION statement on a remote database Execute SYNCHRONIZE SUBSCRIPTION statements at the consolidated database.
Large volume of messages may result Synchronizing databases over a message system can require large volumes of messages. Also, the size of the message can exceed the size of the remote database. Synchronizing many subscriptions over a message link can increase the amount of message traffic.
Often, it is recommended that you extract the remote databases and then manually load the data.
| Discuss this page in DocCommentXchange. Send feedback about this page using email. |
Copyright © 2009, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.1 |