being notified when replication stops

Hello sometimes for communication problems, the replication stops and we
need to Start Synchronizing again. Is there a way I can be notified when
this happens. Because usually I found out that replication stops when users
start calling that they don't see the data from the other sites.
Is there any table that the replication writes everytime the replication
stops for some reason. This way I can select this table every hour and check
if there is an issue with the replication before it's a problem with the
final users.
Thanks in advance
Jennyfer
You can modify the replicatation job to send out notification when it fails.
For each subscription on subscriber , there will be a job which does the
necesary work.
you can modify that job to send otu notification.
hope this helps.
Sam
"Jennyfer J Barco" <pdwhitt@.nospam.wdsinc.com> wrote in message
news:eP3cNAAJFHA.1392@.TK2MSFTNGP10.phx.gbl...
> Hello sometimes for communication problems, the replication stops and we
> need to Start Synchronizing again. Is there a way I can be notified when
> this happens. Because usually I found out that replication stops when
> users
> start calling that they don't see the data from the other sites.
> Is there any table that the replication writes everytime the replication
> stops for some reason. This way I can select this table every hour and
> check
> if there is an issue with the replication before it's a problem with the
> final users.
>
> Thanks in advance
> Jennyfer
>

being notified when replication stops

Jennyfer,
like Sam says, you can add an additional step in your
replication job. This is the way I do it as I have to use
SMTP emails. As an alternative, you might use the inbuilt
Replication: agent failure alert.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
I also have the same problem, i don't need a notification but i want the
agent to start synchronising again...may be after some time ... is it
possible?
"Paul Ibison" wrote:

> Jennyfer,
> like Sam says, you can add an additional step in your
> replication job. This is the way I do it as I have to use
> SMTP emails. As an alternative, you might use the inbuilt
> Replication: agent failure alert.
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>

be notified when connections = 5

I would like to be notified of when my database connection hit 5. That way I know when I ned to upgrade from msde to standard edition. I have the server email ready but not sure how to moniter the connections.Create an alert in performance monitor.|||sounds streight forward thanks.|||The limitation on MSDE is on 5 concurrently running processes. You can periodically check DBCC CONCURRENCYVIOLATION (sp?) to see if you have hit that limit. So long as you keep the queries short, you could concievably keep 20 or 30 people happy enough with the application.|||it is one of those situations where I really do not know how many users I will get at a time. That is why I want to have a way to moniter it. If I have to by the full version fine, if I can hold of awhile great.|||The concurrent workload governor looks at concurrent batches - not connections. Knowing that, I would enable the logging using the DBCC CONCURRENCYVIOLATION(STARTLOG) command and/or use active transactions in the performance monitor.|||ok, great. thanks for the info.