Conflict resolution logs

Is conflict resolution data stored somewhere? For example: If you resolve a
conflict and choose not to have the logs mailed to you. Is there a way to go
back and see what record it was that had the conflict?
TIA
Paul Bauer
Paul,
look for a table whose name starts with 'conflict' and ends with the
article's 'tablename'. This table has the same structure as the table on
which it is based and is stored at the Publisher for applications that use
centralized conflict logging, and at the Subscriber for applications that
use decentralized conflict logging. Another conflict table generated during
merge replication setup is MSmerge_delete_conflicts. The table is a log for
deleted conflicts. It contains information for deleted rows that conflicted
with an update and lost the conflict, or because a delete was undone to
achieve data convergence.
You can look at these tables directly or use the conflict viewer.
HTH,
Paul Ibison
|||Paul,
This table contains no data. I believe this is because the conflict has been
resolved. Is there another place where the resolution of the conflict is
stored?
Paul
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:OX5LN7OhEHA.244@.TK2MSFTNGP10.phx.gbl...
> Paul,
> look for a table whose name starts with 'conflict' and ends with the
> article's 'tablename'. This table has the same structure as the table on
> which it is based and is stored at the Publisher for applications that use
> centralized conflict logging, and at the Subscriber for applications that
> use decentralized conflict logging. Another conflict table generated
> during
> merge replication setup is MSmerge_delete_conflicts. The table is a log
> for
> deleted conflicts. It contains information for deleted rows that
> conflicted
> with an update and lost the conflict, or because a delete was undone to
> achieve data convergence.
> You can look at these tables directly or use the conflict viewer.
> HTH,
> Paul Ibison
>
|||Paul,
resolved conflicts still go into these tables for the conflict viewer. There
are no other tables apart from if you are doing some custom logging (custom
conflict resolution).
HTH,
Paul Ibison

Conflict Management

Hello:
If merge replication uses anonymous pull subscriptions and
the subscribers have no sql server tools installed, how can the
subscribers resolve conflicts? (Can we provide a program interface to
help do this?)
Does replication(merge) preserve transactional integrity
while doing updates to the publisher, if there is a conflict. (That
is, if a updated table, that was updated in a transaction on a
replicated database, conflicts with another replicated database, since
this information waits in conflict tables till resolved, will the
whole transaction wait or will the remaining tables proceed to update
themselves?)
Thanks for the help,
Hananiel
The conflict viewer is one possibility. I believe this ships with Office
2003. The SQL 2000 Resource kit has a chapter devoted to the Conflict
Resolver object. You might want to build your own conflict resolver app.
"Hananiel" <hananiel@.yahoo.com> wrote in message
news:e338e321.0410110813.771d55a8@.posting.google.c om...
> Hello:
> If merge replication uses anonymous pull subscriptions and
> the subscribers have no sql server tools installed, how can the
> subscribers resolve conflicts? (Can we provide a program interface to
> help do this?)
> Does replication(merge) preserve transactional integrity
> while doing updates to the publisher, if there is a conflict. (That
> is, if a updated table, that was updated in a transaction on a
> replicated database, conflicts with another replicated database, since
> this information waits in conflict tables till resolved, will the
> whole transaction wait or will the remaining tables proceed to update
> themselves?)
> Thanks for the help,
> Hananiel