We are seeing unexpected behavior in transactional peer-to-peer replication

  • Hi

    Sorry for asking what may be a rookie question... We have configured transactional peer-to-peer replication in a testing environment with two servers, each publishing and subscribing to each other. If we write a piece of code that updates the same row on both servers with different values, we are not seeing data conflict issues. The data updated on server 1 propagates to server 2, but at the same time data updated on server 2 is updated on server 1. This leaves the records on each server out of data.

    I expected my test case to produce errors, but instead I got inconsistent data. How do you turn on data consistency checking?

    Thanks in advance

  • By design peer to peer does not have conflict resolution...

    If you update the same row on both servers data will be wiped out by each other...

     

    MohammedU
    Microsoft SQL Server MVP

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply