My environment is comprising of 2 SQL servers setup with P2P replication in SQL 2008,ÃÂ 2 Web servers connect to only one SQL server at a time and make changes to the published tables andÃÂ 2 Application servers which connects to both the SQL servers all the timeÃÂ but they only read data.
We chose P2P since my app servers are in different locations which read data from both the SQL servers and we use it as HA solution.
Since we are changing data at only one SQL server, thought we should never get update-update conflicts but we are now on the same node.
A conflict of type 'Update-Update' was detected at peer 3 between peer 1 (incoming), transaction id 0x0000000000725ca2 and peer 1 (on disk), transaction id 0x00000000007259e9 (Source: MSSQLServer, Error number: 22815)
We are making changes only at Server A and Server B is my backup server.
I made a varchar field updated in 1 row on a table in server A then it getsÃÂ replicated to Server B
then I made the same field updated for 160 rows on the same table in Server A then it gets replicated to Server B
then I reverted back the change made to the field on all 160 rows on the same table in Server A then my replication failing with Update-Update conflict.
I'm not sure whats causing this because I'm not making any change
View Complete Post