Queued updating replication

Reinitializing the Subscriber to resolve conflicts maintains strict transactional consistency at the Subscriber, but it can be time consuming if the publication contains large amounts of data.When the Queue Reader Agent detects a conflict, all remaining transactions in the queue (including the transaction in conflict) are rejected, and the Subscriber is marked for reinitialization.In this case, another Subscriber or the Publisher updated the same row in the publication before this Subscriber transaction was synchronized.

queued updating replication-64

The next snapshot generated for the publication is applied by the Distribution Agent to the Subscriber.

Conflict detection under the Subscriber wins policy means the last Subscriber transaction to update the Publisher wins.

Microsoft is conducting an online survey to understand your opinion of the Msdn Web site.

If you choose to participate, the online survey will be presented to you when you leave the Msdn Web site.

Transactional replication is implemented by the SQL Server Snapshot Agent, Log Reader Agent, and Distribution Agent.