Setting up the merge agents
The synchronization process in merge replication ensures that data at the Publisher and Subscribers eventually converge and that all sites end up with the same data values. However, the sites are never completely synchronized unless there is a period of complete inactivity in iBase.
The best way to ensure that the sites are as closely synchronized as possible is to set a low polling interval, particularly for the entity and link data, for example a 1 second polling interval. Different considerations will apply for the iBase security data and audit log.
The SQLServerAgent service should be set to auto-start whenever the operating system starts.
Configuring the Merge Agent to run continuously
This parameter specifies that the agent queries the Publisher or Subscriber for data changes at the specified interval, even if there are no updates pending.
You also need to set the polling interval as described in the following information.
Merge Agent for the entity and link database
Start or restart the agent to use the new agent properties.
Merge Agent for the security database
- How often does the user data in the security database change?
- How quickly must changes be replicated to other sites?
Merge Agent for the audit log
- How often analysts consult the audit log
- How long it takes for a problem to be identified and for analysts to decide to review the audit log
- The audit level of the database
Merge Agent for a read-only database
Configure the Merge Agent for a read-only iBase database to prevent any changes made at the Subscriber from being uploaded to the Publisher. For example, changes made through SQL Server Query Analyzer.
To reconfigure the Merge Agent, add this parameter to the Run Agent command line:
The argument specifies that the agent only downloads data changes from the Publisher to the Subscriber.