Is there a way I can be notified when a merge replication resolves/shows a
conflict. Maybe e-mail or something?
Thanks,
Steve
There is interactive conflict resolution. You could also have a job which
will run and query the conflict tables, or place triggers on the conflict
tables
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
"SteveInBeloit" <SteveInBeloit@.discussions.microsoft.com> wrote in message
news:9BA89624-D1FA-4C6D-90ED-13FA51D4F5F4@.microsoft.com...
> Is there a way I can be notified when a merge replication resolves/shows a
> conflict. Maybe e-mail or something?
> Thanks,
> Steve
|||Thanks Hilary,
When do the rows from the conflict tables get deleted? Ours are always
empty. We do have the snapshot agent running every night, is that doing it?
Thanks,
Steve
"Hilary Cotter" wrote:
> There is interactive conflict resolution. You could also have a job which
> will run and query the conflict tables, or place triggers on the conflict
> tables
> --
> 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
> "SteveInBeloit" <SteveInBeloit@.discussions.microsoft.com> wrote in message
> news:9BA89624-D1FA-4C6D-90ED-13FA51D4F5F4@.microsoft.com...
>
>
|||IIRC they are purged when the history retention period has passed.
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
"SteveInBeloit" <SteveInBeloit@.discussions.microsoft.com> wrote in message
news:2BB8DB35-8636-4EFD-868F-0A9BBA4AFB00@.microsoft.com...[vbcol=seagreen]
> Thanks Hilary,
> When do the rows from the conflict tables get deleted? Ours are always
> empty. We do have the snapshot agent running every night, is that doing
> it?
> Thanks,
> Steve
> "Hilary Cotter" wrote:
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment