could you please suggest me the way I could automatically resolve
primary key conflicts during a merge between Publisher and Subscriber. It seems Sql Server doesn’t do it out of the box :(.
Conflict viewer shows me next message:
A row insert at ‘_publisher_server_’ could not be propagated to ‘_subscriber_server_’. This failure can be caused by a constraint violation. Violation of PRIMARY KEY constraint ‘PK_PartPlan_FD9D7F927172C0B5′. Cannot insert duplicate key in object ‘_table_name_’.
Thank you.
This isn’t an easy solution (since you’ve presumably already designed your database with auto-incrementing
intkeys), but using GUID (“uniqueidentifier”) for your primary keys will solve your PK collision problem.