Merge Replication and Multiple Record UPDATE statements

We have a database in which global updates must be periodically made to
multiple records, usually in the hundreds or thousands.
Is this a problem when using Merge replication? Because there are individual
merge triggers on each table, is it preferable to use a cursor to make global
changes?
Also, when using View Conflicts feature, is it safe to assume that record
listed as the winner has already been replicated to all locations? If so, why
does one have to click on either the Keep Winning Change or the Resolve With
This Data button?
Is there a way to globally accept all winning changes?
The global update will take far longer with merge replication. A cursor
solution might offer better performance.
Regarding the conflict viewer, it is safe to assume that the conflict has
been resolved with the publisher and one subscriber. It might then conflict
with another subscriber, so you can't assume it has been resolved
everywhere.
The keep winning change button and the resolve with this data buttons allow
you to clear the conflict (in other words accept it) or roll it back and let
the subscribers change win.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"elpepe" <elpepe@.discussions.microsoft.com> wrote in message
news:D5C598DA-05F0-4F98-A869-DA53D058D628@.microsoft.com...
> We have a database in which global updates must be periodically made to
> multiple records, usually in the hundreds or thousands.
> Is this a problem when using Merge replication? Because there are
> individual
> merge triggers on each table, is it preferable to use a cursor to make
> global
> changes?
> Also, when using View Conflicts feature, is it safe to assume that record
> listed as the winner has already been replicated to all locations? If so,
> why
> does one have to click on either the Keep Winning Change or the Resolve
> With
> This Data button?
> Is there a way to globally accept all winning changes?
|||Thanks -- that's very helpful.
There are hundreds of conflicts that remain. Is there a way to globally
accept the winner so that the conflicts are resolved everywhere?
Also, will you be writing a book on Merge replication anytime soon?
"Hilary Cotter" wrote:

> The global update will take far longer with merge replication. A cursor
> solution might offer better performance.
> Regarding the conflict viewer, it is safe to assume that the conflict has
> been resolved with the publisher and one subscriber. It might then conflict
> with another subscriber, so you can't assume it has been resolved
> everywhere.
> The keep winning change button and the resolve with this data buttons allow
> you to clear the conflict (in other words accept it) or roll it back and let
> the subscribers change win.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "elpepe" <elpepe@.discussions.microsoft.com> wrote in message
> news:D5C598DA-05F0-4F98-A869-DA53D058D628@.microsoft.com...
>
>