How does web synchronization work for Merge Replication?
Web synchronization is an option only for pull subscriptions; therefore, a Merge Agent will always run on the Subscriber. This Merge Agent can be the standard Merge Agent, the Merge Agent ActiveX control, or an application that provides synchronization through Replication Management Objects (RMO).
What happens to the merge agent during synchronization?
The following steps occur during synchronization: The Merge Agent is started at the Subscriber. The agent does the following: Makes an SQL connection to the subscription database. Extracts any changes from the database. Makes an HTTPS request to the computer that is running IIS. Uploads data changes as an XML message.
What does merge replication Reconciler do on IIS?
The SQL Server Replication Listener and Merge Replication Reconciler that are hosted on the computer that is running IIS do the following: Respond to the HTTPS request. Make an SQL connection to the publication database.
What is the purpose of web synchronization in IIS?
Web synchronization is not intended for high-volume server-to-server applications. When Web synchronization is used, updates at the Subscriber are packaged and sent as an XML message to the computer that is running IIS by using the HTTPS protocol.
How is a subscription synchronized in SQL Server?
Subscriptions are synchronized by the Distribution Agent (for snapshot and transactional replication) or the Merge Agent (for merge replication). Agents can run continuously, run on demand, or run on a schedule.
How is snapshot replication used in SQL Server?
The snapshot replication is used to provide an initial set of database objects for merge or transaction publications. It can copy and distribute database objects in the same manner as they appear at the current moment. It is used to give an initial set of data for merge and transactional replication.