Replication Monitoring

SQL Server 2000 EE.
What is the best way to monitor replication and have it send an email to me
as soon as it fails for some reason ? Is there a 3rd party utility for better
monitoring ?
Thanks.
You can utilize internal sql mail (if you have it configured). When
you setup your publications and subscriptions sql2000 will generate
jobs. In jobs properties you can set it to send you an e-mail if it
fails.
You can also write custom jobs to do this for you:
http://msdn2.microsoft.com/en-us/library/ms147874.aspx
T.
DXC wrote:
> SQL Server 2000 EE.
> What is the best way to monitor replication and have it send an email to me
> as soon as it fails for some reason ? Is there a 3rd party utility for better
> monitoring ?
> Thanks.
|||There are some built-in alerts for replication monitoring. In particular
there is the "Replication: agent failure" alert - you could enable this and
on the response tab select an operator to notify. For a more granular
approach you could identify the replication jobs themselves and define
operators to send emails to if the job fails.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .

Replication Monitoring

SQL Server 2000 EE.
What is the best way to monitor replication and have it send an email to me
as soon as it fails for some reason ? Is there a 3rd party utility for bette
r
monitoring ?
Thanks.You can utilize internal sql mail (if you have it configured). When
you setup your publications and subscriptions sql2000 will generate
jobs. In jobs properties you can set it to send you an e-mail if it
fails.
You can also write custom jobs to do this for you:
http://msdn2.microsoft.com/en-us/library/ms147874.aspx
T.
DXC wrote:
> SQL Server 2000 EE.
> What is the best way to monitor replication and have it send an email to m
e
> as soon as it fails for some reason ? Is there a 3rd party utility for bet
ter
> monitoring ?
> Thanks.|||There are some built-in alerts for replication monitoring. In particular
there is the "Replication: agent failure" alert - you could enable this and
on the response tab select an operator to notify. For a more granular
approach you could identify the replication jobs themselves and define
operators to send emails to if the job fails.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .

Replication Monitoring

What would be a best practice for monitoring Replication?
I have Transactional Replication going from the Production database (SQL00) to the Reporting database (SQL03).
Are there some Alerts I need to make sure I have setup to notify me?
Should I do a Validate Subscription once a week or so?
What would you do to have peace of mind that your reporting database is exactly in sync with your production database?
Thanx!
This depends on the stability of your links. If you are well connected, i.e. have highly reliable links set up the replication alerts to alert you when your job fails.
If your links are somewhat unstable set up the replication alerts to alert you when a job fails, but make sure you click on the response tab, and set a threshold to be alerted at, i.e. once per day, hour, etc.
You can schedule validations using sp_publication_validation. Use this proc in conjunction with the Replication: Subscriber has failed data validation alert.
How frequently you wish to run a validation depends on what you are doing. In general with a read only subscriber I never feel the need to run one. Your comfort level (or your bosses') might vary from mine.
With an updateable subscriber (immediate, queued, or merge) you might feel the need to run validations more often.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23juwUyqjEHA.2764@.TK2MSFTNGP11.phx.gbl...
What would be a best practice for monitoring Replication?
I have Transactional Replication going from the Production database (SQL00) to the Reporting database (SQL03).
Are there some Alerts I need to make sure I have setup to notify me?
Should I do a Validate Subscription once a week or so?
What would you do to have peace of mind that your reporting database is exactly in sync with your production database?
Thanx!

replication monitoring

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..
>

Replication Loop Back Detection Problems in SQL Server 2000

Hi,

I am monitoring my replication process and I have a problem with the loop detection, I can see origined transacctions in the server, executed in the same for the replication.

The subscriptions configuration is sp_helpsubscription

exec sp_addsubscription @.publication = N'PUBLICATION',
@.article = N'all',
@.subscriber = N'192.168.0.23',
@.destination_db = N'PRUEBABD',
@.sync_type = N'none',
@.update_mode = N'read only',
@.offloadagent = 0,
@.dts_package_location = N'distributor',
@.loopback_detection = 'true'
GO

I need for help.

Sorry, it's not clear to me what the problem is. Are you getting an error of some sort?|||

Yes, I have loops in the replication between the subscribers and too many deadlocks.

My topology is

Server A replicates to Server P,

the Server P replicates to Server A,

Server B replicates to Server P and

the Server P replicates to Server B.

I am using transactional replication,

|||sorry, i'm still not clear. what exactly is the error. if it's deadlock, what statements are deadlocking?|||My problem is that loop back detection is unless when I registed the subscriptions with IP. The publicator servers are registered for name.