Click here to Skip to main content
15,890,845 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
Hi there ,

I have set up a Merge replication on the SQL server 2008 R2 . Which exchanges all rows that have changed between the Publisher and Subscriber since the last time synchronization occurred.

here is one scenario i want to ask you guys about. What happens when the Publisher and Subscriber have a row in a table with same primary key but different Row GUID. The row in the subscriber is newer and created later.

Here when i syncronize the row at the server gets deleted. why should this happen ? any logical explanation?

i Know for fact that the rows at server and client should have the same GUID's.

With regards,
Saurabh
Posted

1 solution

The GUID should be the primary key. That would be the point of using them, your clients can create new rows that remain unique when synched to the server.
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900