A Subscriber can perform inserts, updates, and deletes on published data only if it can perform a two-phase commit protocol (2PC) transaction with the Publisher.
Initiates 2PC automatically.
Replicates the committed update down to all other Subscribers through the standard snapshot or transactional replication mechanism.
Uses a timestamp column (not datetime) to perform conflict detection at the Publisher.
Lets the originating Subscriber continue working without waiting for the successful update to trickle down.
Forestalls the requirement for the updating Subscriber to have a distribution database or log reader and get involved in the administrative issues of replication publishing.
Has fewer failure points with every site than with full 2PC.
Guarantees no loss of transactional consistency.
Demands that the Subscriber making changes and the Publisher are well-connected, although other Subscribers do not have to be well-connected at the time the changes are made.
Scales upward because it preserves an orderly system.
Registers a timestamp column in the published table. If a timestamp column does not already exist in the table, Microsoft® SQL Server™ adds one automatically.