Re: "publisher always wins conflict" resolver? (for merge replication under SQL 2000)

It sounds like it is only occuring on a subset of tables. In this case you need to run profiler on the publisher and subscriber to narrow down the DML which is causing this.

Could you post the problem table schemas here and possibly the publication/subscription script so we can try to repro this?


"tbh" <femdev@xxxxxxxxxxxxxxxxx> wrote in message news:ON0e$TesIHA.3604@xxxxxxxxxxxxxxxxxxxxxxx
thanks!

"Hilary Cotter" <hilary.cotter@xxxxxxxxx> wrote in message news:85FBC07D-1800-4379-9DB2-451517FED250@xxxxxxxxxxxxxxxx
there are basically 3 types of conflicts -pk violations (insert conflicts
...
Are these deletes showing up in the conflict viewer?

yes, and it says the delete wins. however, as I mentioned, no one should be deleting these at the subscriber (and i failed to find them with a profiler running [*]) so we are at a loss to explain them.

cheers, Tim

[*] i am unclear what all i might need to include in my profiler in order to see
- an insert accomplished via replication
- an insert done via linked server (i tried this initially, but later did a much simpler insert locally)
- whatever phantom "delete" might be happening (because of an RI constraint that rears its head during replication??)



.

Relevant Pages
Loading