Queued updating subscriptions
fighter pilot dating
The conflicting transaction is rolled back at the Subscriber that initiated it.We recommend that you use peer-to-peer transactional replication instead.However, I just can't find the replication type Transactional publication with updatable subscriptions on the publication type page in SQL Server 2012, see the image below: Anyone can confirm, whether we have this feature in SQL Server 2012? The Queue Reader Agent uses this column during synchronization to determine if a conflict exists.
A transaction in a queue maintains the old and new row version values.
The Queue Reader Agent detects a conflict and compensating commands are generated and propagated to the Subscriber by posting them in the distribution database.