OK Chaps get your thinking caps on
We have a program that sends out email via DBMail. Last week the mail servers went down and the only way I found out about it was I happened to be working on a SSIS package that used DBMail. The annoying thing was the NT guys knew about it but did'nt inform us.
On the program in qusetion I can look at the failed messages table and look for consecutive groups of emails that have failed which would indicate the mail server is down. This can be put into a job that runs every hour. Can you think of a way I can inform myself and the other DBAs of the failiure without using NET Send as it is disabled on our system. Obviously I can't send myself an email as the server is down.
We have a program that sends out email via DBMail. Last week the mail servers went down and the only way I found out about it was I happened to be working on a SSIS package that used DBMail. The annoying thing was the NT guys knew about it but did'nt inform us.
On the program in qusetion I can look at the failed messages table and look for consecutive groups of emails that have failed which would indicate the mail server is down. This can be put into a job that runs every hour. Can you think of a way I can inform myself and the other DBAs of the failiure without using NET Send as it is disabled on our system. Obviously I can't send myself an email as the server is down.