Hi SQL server expert,
I have a merge replication. The table has a primary key and an identity
column.
when I insert one row at the publisher and one row at the subscriber with
the same key,
I got two conflicts after syncronization, nothing got syncronized. What I
would like it to do was to let the publisher win. The row at the subsriber
side becomes the same as the publisher side, that is same primary key should
have the same identity column.
I use server subscription. But the default resolver does not seem to do
anything. Please help me.
Pingx
Pingx - 18 Jul 2008 01:44 GMT
I just tried to create a new replication. replaced the identity column with
an INT column. The problem still happens. The resolver does not do anything
to solve the conflict. Please help.
> Hi SQL server expert,
>
[quoted text clipped - 10 lines]
>
> Pingx
Hilary Cotter - 18 Jul 2008 16:25 GMT
What version of SQL Server are you running?
With SQL Server 2000 sp3 introduced compensate_for_errors on
sp_addmergearticle which will cause subscriber generated conflicts to
resolve with their value. Make sure this is set to false in your case.
> Hi SQL server expert,
>
[quoted text clipped - 12 lines]
>
> Pingx
Pingx - 29 Jul 2008 05:48 GMT
I'm using sql server 2005.
I did not use sp_addmergearticle to add an article. I added the article
using GUI when creating the publisher.
Can I use this to resolve the conflict?