Sql Server merge replication primary key violations?

I'd change the IDENTITY so one is odd, one even. Or -ve/+ve.

I'd change the IDENTITY so one is odd, one even. Or -ve/+ve. Probably the simplest way to do it... Edit: I assumed identity PK columns.

I'd suggest you update the question with the relevant info contained in the comment. It's incomplete otherwise. You said "The desired behaviour is that after the merge all rows are identical.

The first one to the publisher wins..." This sounds like conflict resolution, which is how you'd deal with PK collisions.

This isn't an replication/identity problem. The primary key is a composite of two varchar columns - there is no way to change this. There can be N subscribers.

Frequently the subscribers will all add an identical row simultaneously. Identical in terms of the PK not the guid since that's randomly generated. The desired behaviour is that after the merge all rows are identical.

The first one to the publisher wins and all other subscription clients then delete their row with the same PK and update to the row from the subscriber that won. I don't want dupped PKs distinguised by IDENTITY col – Gary Dec 17 '09 at 22:55.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.