Sql server replication queued updating

03-Feb-2018 11:32

If the old GUID stored in the transaction does not match the GUID in the publication, a conflict is detected.

When data is updated at a Subscriber, it is first propagated to the Publisher and then propagated to other Subscribers.

Deprecated features should not be used in new applications.

Conflicts are detected and resolved according to a conflict resolution policy that is set when creating the publication.If the old GUID stored in the transaction matches the GUID in the publication, the publication is updated and the row is assigned the new GUID that was generated by the Subscriber.By updating the publication with the GUID from the transaction, you have matching row versions in the publication and in the transaction.This feature will be removed in a future version of Microsoft SQL Server.

Avoid using this feature in new development work, and plan to modify applications that currently use this feature.

We recommend that you use peer-to-peer transactional replication instead.