check replication conflicts programmatically

Hi,
I would like to know if we can check merge replication conflicts
programmatically.
which tables do we need to check for replication conflicts?
By default some conflict_* tables are created. will these contain the
info?
Rgds,
amit
mitsql,
yes the conflict_ tables contain the necessary information. In detail
they contain the column values of the losing replication partner plus
the reason for the conflict and the guid. If you want to be notified
when a conflict occurs you can create an insert trigger on the conflict
tables which either sends a mail or runs some sript/store procedure.
Markus
sql

check replication conflicts programmatically

Hi,
I would like to know if we can check merge replication conflicts
programmatically.
which tables do we need to check for replication conflicts?
By default some conflict_* tables are created. will these contain the
info?
Rgds,
amitmitsql,
yes the conflict_ tables contain the necessary information. In detail
they contain the column values of the losing replication partner plus
the reason for the conflict and the guid. If you want to be notified
when a conflict occurs you can create an insert trigger on the conflict
tables which either sends a mail or runs some sript/store procedure.
Markus

check replication conflicts programmatically

Hi,
I would like to know if we can check merge replication conflicts
programmatically.
which tables do we need to check for replication conflicts?
By default some conflict_* tables are created. will these contain the
info?
Rgds,
amitmitsql,
yes the conflict_ tables contain the necessary information. In detail
they contain the column values of the losing replication partner plus
the reason for the conflict and the guid. If you want to be notified
when a conflict occurs you can create an insert trigger on the conflict
tables which either sends a mail or runs some sript/store procedure.
Markus

Check on Replication

i,
I have the following scenario:
One server (Publisher) is in one domain "Domain A" and the other server
(Subscriber) is in a different domain "Domain B"; the mail server is in
"Domain A" for which the subscriber is unable to send email notifications
toward any user in "Domain A".
Because of the above it's difficult for us to monitor the status of the
replication and so far we just learn that the replication is down generally
hours later it's happened.
Is there any way to check out the status of the replication from the
publisher?query the msrepl_errors table on the distribution database. If you are using
pull replication you could query the msdistribution_view to check to see if
commands are pooling. You can find this view in the distribution database.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"FJC" <FJC@.discussions.microsoft.com> wrote in message
news:37B0A8A1-FC72-443A-AC15-14A76CE3ADCD@.microsoft.com...
> i,
> I have the following scenario:
> One server (Publisher) is in one domain "Domain A" and the other server
> (Subscriber) is in a different domain "Domain B"; the mail server is in
> "Domain A" for which the subscriber is unable to send email notifications
> toward any user in "Domain A".
> Because of the above it's difficult for us to monitor the status of the
> replication and so far we just learn that the replication is down
> generally
> hours later it's happened.
> Is there any way to check out the status of the replication from the
> publisher?|||query the msrepl_errors table on the distribution database. If you are using
pull replication you could query the msdistribution_view to check to see if
commands are pooling. You can find this view in the distribution database.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"FJC" <FJC@.discussions.microsoft.com> wrote in message
news:37B0A8A1-FC72-443A-AC15-14A76CE3ADCD@.microsoft.com...
> i,
> I have the following scenario:
> One server (Publisher) is in one domain "Domain A" and the other server
> (Subscriber) is in a different domain "Domain B"; the mail server is in
> "Domain A" for which the subscriber is unable to send email notifications
> toward any user in "Domain A".
> Because of the above it's difficult for us to monitor the status of the
> replication and so far we just learn that the replication is down
> generally
> hours later it's happened.
> Is there any way to check out the status of the replication from the
> publisher?

Check on Replication

i,
I have the following scenario:
One server (Publisher) is in one domain "Domain A" and the other server
(Subscriber) is in a different domain "Domain B"; the mail server is in
"Domain A" for which the subscriber is unable to send email notifications
toward any user in "Domain A".
Because of the above it's difficult for us to monitor the status of the
replication and so far we just learn that the replication is down generally
hours later it's happened.
Is there any way to check out the status of the replication from the
publisher?query the msrepl_errors table on the distribution database. If you are using
pull replication you could query the msdistribution_view to check to see if
commands are pooling. You can find this view in the distribution database.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"FJC" <FJC@.discussions.microsoft.com> wrote in message
news:37B0A8A1-FC72-443A-AC15-14A76CE3ADCD@.microsoft.com...
> i,
> I have the following scenario:
> One server (Publisher) is in one domain "Domain A" and the other server
> (Subscriber) is in a different domain "Domain B"; the mail server is in
> "Domain A" for which the subscriber is unable to send email notifications
> toward any user in "Domain A".
> Because of the above it's difficult for us to monitor the status of the
> replication and so far we just learn that the replication is down
> generally
> hours later it's happened.
> Is there any way to check out the status of the replication from the
> publisher?

check merge replication conflicts

Hi,
I would like to know if we can check merge replication conflicts
programmatically.
which tables do we need to check for replication conflicts?
By default some conflict_* tables are created. will these contain the
info?
Rgds,
amit
Yes - these custom-named tables and MSmerge_delete_conflicts will contain
the info you require.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||thanks a lot.

check if distribution agent has independent agent set

How can i check if my distribution agent has the independent agent option
enabled during transactional replication ?
check the publication using sp_helppublication.
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

Check constraint for identity range

Hi,
When I delete subscriptions and publications and disable the replication,
the check constraint for identity range stays in subscriber for tables. Then
I have to manually drop or disable them. Is it an expected behavior or
there's something wrong in my work? How can I have them removed
automatically?
Thanks in advance,
Leila
I reported this problem to Microsoft already. From what I understand this
request was unanticipated by the design team. They expected that when you
replicate to a subscriber, the publisher subscriber relationship is forever.
They did not anticipate customers breaking replication and then using the
subscriber as a standalone database.
I did post a script here sometime ago to remove these constraints.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Leila" <Leilas@.hotpop.com> wrote in message
news:ecnVFp18EHA.808@.TK2MSFTNGP10.phx.gbl...
> Hi,
> When I delete subscriptions and publications and disable the replication,
> the check constraint for identity range stays in subscriber for tables.
Then
> I have to manually drop or disable them. Is it an expected behavior or
> there's something wrong in my work? How can I have them removed
> automatically?
> Thanks in advance,
> Leila
>
|||Thanks Hilary,
Could you please post a link to your script again.
Thanks again,
Leila
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uXYke518EHA.1392@.tk2msftngp13.phx.gbl...
>I reported this problem to Microsoft already. From what I understand this
> request was unanticipated by the design team. They expected that when you
> replicate to a subscriber, the publisher subscriber relationship is
> forever.
> They did not anticipate customers breaking replication and then using the
> subscriber as a standalone database.
> I did post a script here sometime ago to remove these constraints.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> "Leila" <Leilas@.hotpop.com> wrote in message
> news:ecnVFp18EHA.808@.TK2MSFTNGP10.phx.gbl...
> Then
>