Agent failures and custom alerting

Hi

I need to have a reliable alerting system for my merge replications I have setup on my MSSQL 2005 server.

The problem is that the build-in alert system the 'agent failure' alert only triggers when 'all databases' for that specific alert is selected. There is no failure alert triggered when I select a database and force a failure. The 'agent succes' alert does never get triggered at all.

I need an reliable succes and failure alert per database because I need to do specific actions per database.

Can someone help me out here?

I'm thinking of building my own alerting system if the help here is insufficient. In that case I need to know in what tables to look. Maybe someone can give me some pointers?

Thanks anyway,

Edward

Have you tried through "Configure Replication Alerts" dialog?

Launch Sqlmonitor.exe --> Expanding publisher and publications --> L-Click a publication --> Warning and Agents Page > Configure Replication Alerts Dialog

It can configure all kinds of alerts, including agent success alert etc. You can try.

Thanks

Yunjing

|||

Thanks for your answer. I know how to configure alerts. Thats not the problem.
The problem is that the 'failure' alert only gets triggered when you select 'all databases' and that the 'Success' alert not gets triggered at all.

I need to trigger the 'Failure' alert per database

I need to trigger the 'success' alert per database

It aint working.

|||

Alert will be triggered per event. It can not be configured per database.

For example, push merge agent run on distributor and pull merge agent run on subscriber. If you set aleart per database, like per subscription db, then some error happened on distribution db won't be catched. It doesn't make sense.

As for some 'Success' alert, replication agent cut some alerts for SQL 2005. LIke if you configure alert for 'Replication Agent Success', these alerts will not be triggered, since some customers complained that too many default alerts are triggered, even for success agent run, and they don't care about success but failure and critical performance etc only.

In the next version of SQL Server, we will address this issue and provide better solution.

Hope the above information will help.

Thanks

Yunjing

|||

Hi Yunjing

Thanks for your help. As you can imagine i'm not really helped. The next version of MSSQL will probably out in 4 years or something.

The strange thing is that everything works fine if the 'merge replication' is NOT in continious mode. Unfortunately this is not the desirable mode.

|||

Hi Yunjing

I was wondering (because of the SP2 update last week) if this issue is adressed?

I cross my fingers..

Thanks anyway

Ed