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

thanks, Hilary, i appreciate your effort.

if i understand your example correctly, you do updates on two subscribers
that lead to conflicts. that makes sense. however, in our case, updates
should happen only on the publisher. we do a single insert at the publisher
which leads to a conflict.

is it possible to run a utility to check what is broken here? (e.g. one that
checks DB consistency across publisher and subscriber?) presumably the
problem might go away if we rebuilt the replication (though I'm skeptical,
since the problem happens on any of the subscribers.) moreover, this is a
major operation which typically requires an admin to work for many hours and
it's a huge drag on the databases.

cheers, Tim

"Hilary Cotter" <hilary.cotter@xxxxxxxxx> wrote in message
news:08E78265-7ACB-4DB8-A62A-C951C8B2AE0F@xxxxxxxxxxxxxxxx
Oops, bad example - this one shows the publisher winning.

update sub1.dbo.doc set charcol='sub1 - 1'
waitfor delay '00:00:10'
update sub2.dbo.doc set charcol='sub2 - 1'
waitfor delay '00:00:10'
update pub.dbo.doc set charcol='pub - 1'
GO
....


.

Relevant Pages

  • Re: "publisher always wins conflict" resolver? (for merge replication under SQL 2000)
    ... It appears you do an insert in the publisher which causes a conflict on the subscribers. ... if i understand your example correctly, you do updates on two subscribers that lead to conflicts. ...
    (microsoft.public.sqlserver.replication)
  • Re: "publisher always wins conflict" resolver? (for merge replication under SQL 2000)
    ... there are basically 3 types of conflicts -pk violations, update conficts - same row updated onboth sides or same column updated on both sides when you are using column level tracking, update/delete conflicts - row is updated on one side, deleted on the other. ... This is the default for the client subscription type - the first to the publisher will win against any other conflicts generated by other subscribers. ... - Microsoft SQL Server Subscriber Always Wins Conflict Resolver ...
    (microsoft.public.sqlserver.replication)
  • sp_MSupd never execute, only sp_MSdel and sp_MSins
    ... The data changes that are made in the article at the Publisher are applied ... with deletes and inserts at the Subscribers, never updates. ...
    (microsoft.public.sqlserver.replication)
  • Re: Unable to retain password for Outlook/ Express
    ... not done the service pak updates. ... software conflicts) they may charge you for fixing the ... Microsoft claims that since the XP ... >responsibility to take care of the problem. ...
    (microsoft.public.windowsxp.security_admin)
  • RE: Data loss when using merge replication
    ... the retention period of subscribers will ... Again assuming that you have conflicts, ... conflict resolution but a smaller set of alternative resolvers. ...
    (microsoft.public.sqlserver.replication)