I have one SQL Server 7 publisher and four SQL Server 7 subscribers
with merge replication (pull). From time to time I get conflicts in
tables with the reason, that a record which was inserted in the
subscriber database couldn't
be inserted in the publishers db due to a FK constraint. The record
then seems to be deleted from the subscriber. I figure the conflicts
occur because the FK constraints are enabled during replication. I
then use Conflict Viewer to insert the conflicting data into the
publisher db and it works fine. The FK conflicts don't exist anymore
so I guess the replication order (table order) must have caused the
problem. Atleast that's what I thought.
But... When I run the merge replication again the same conflicts are
back and the conflicting records are deleted from the publisher! If I
instead script the conflicting data into the publisher's db and then
run the merge replication everything works fine.
Should FK constraints be enabled during replication?
How come the conflicts come back when they are resolved successfully?
Why are the conflicting records deleted?