Compensating Changes - Deletes Good Rows From a Table?

We have some tables set up doing merge replication, and just came across
http://support.microsoft.com/default...&Product=sql2k
Is this gist of this, that when a compensating change condition exists, that
potentially good rows that cannot be replicated out, are instead DELETED
from the source table?
Is it logged somewhere when this has happened, or is there a way to monitor
it otherwise?
Thanks!
They are logged as conflicts but remain in the publisher/subscriber.
So if you insert a row with the same pk value in the publisher and
subscriber, when the sync happens the rows remain in the publisher and
subscriber.
If you update a row on the subscriber and delete it on the publisher, the
row remains updated on the subscriber and is not deleted there and remains
deleted on the publisher.
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
"Art Vandelay" <artvandelay92k@.hotmail.com> wrote in message
news:OR2q7S6%23FHA.264@.tk2msftngp13.phx.gbl...
> We have some tables set up doing merge replication, and just came across
> http://support.microsoft.com/default...&Product=sql2k
> Is this gist of this, that when a compensating change condition exists,
> that potentially good rows that cannot be replicated out, are instead
> DELETED from the source table?
> Is it logged somewhere when this has happened, or is there a way to
> monitor it otherwise?
> Thanks!
>
>
>