all groups > sql server replication > february 2004 >
You're in the

sql server replication

group:

Unresolved conflict in the replication



Unresolved conflict in the replication SHARAD
2/20/2004 8:14:09 AM
sql server replication: Dear friends

I have got the following unresolved conflict for the
replication. We are using the merge replication.

Datetime,UserAction,Database,Publication,Table,Origin_Data
Source,RowGuidValue,conflict_type,reason_text,SQL
20/02/2004 15:45:58,"Conflict
Loser","MainSQL","BPOMainSQL","[dbo].
[SAL2004]","cool.BPOSQL","{E69DDB18-4BAF-45E4-8006-
E90BF8914AA9}","5","The row was inserted at 'COOL.BPOSQL'
but could not be inserted at 'MATRIX.MainSQL'. Violation
of PRIMARY KEY constraint 'PK__SAL1__03FB8544'. Cannot
insert duplicate key in object 'SAL2004'.","",

Please suggest what action i should take to solve the
problem.

Best regards
RE: Unresolved conflict in the replication Paul Ibison
2/20/2004 9:16:07 AM
Sharad
you could partition the data to make sure each subscriber and the publisher receive different primary key values. This could be done using identity ranges for a surrogate PK or by having a multi-column PK, one column of which has a site identifier
HTH
AddThis Social Bookmark Button