How do u check for replication latencies or if say the log reader or
distribution agent has stopped due to some failures ? Is there an easy way
to track this without buying some 3rd party tool. How can one write a query
? Love to hear some of ur ways of detecting delays in replications..
To check for failures use replication alerts.
It is extremely rare to see log reader agents not keeping up. If want to
check you can use sp_repltrans and fire an alert if rows are returned. You
can also query MSDistribution_status and raise an alert if you are getting
too far behind.
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:umLppaVSFHA.3288@.TK2MSFTNGP14.phx.gbl...
> How do u check for replication latencies or if say the log reader or
> distribution agent has stopped due to some failures ? Is there an easy way
> to track this without buying some 3rd party tool. How can one write a
query
> ? Love to hear some of ur ways of detecting delays in replications..
>
Wednesday, March 7, 2012
replication monitoring
Labels:
agent,
database,
due,
failures,
latencies,
log,
microsoft,
monitoring,
mysql,
oracle,
ordistribution,
replication,
server,
sql,
wayto
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment