Sql Server merge replication primary key violations Using Sql Server 2008.  Pretend I have a publisher and 2 subscribers A and B.  The replicated table has a guid on it and also a primary key that is not the guid.  Frequently, updates happen at both subscribers near simultaneously generating 2 different guids but the same primary key.  Then when they go to syncronize I get primary key violation errors.  

Thinking of ways to resolve this - having the guid be generated based on the primary key or having replication use the primary key instead of guid (that seems hard/silly) or as a last resort have replication just continue on and ignore those violations.

Which route should I take?
I'd change the IDENTITY so one is odd, one even. Or negative/positive.

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.