Recently, one of our database went offline and EM showed it as Suspect. We got to know about it only when the users couldn't logon to the site. If something like that happens in the future, I'd like to trap any error that SQL Server 2000 would throw, and set off a mail to the administrators informing them that that's what's wrong. One of the solutions that I am trying to implement will use CDOSYS (The SQL box runs on a cluster and SQL Mail behaves erratically on the cluster. So, the use for CDOSYS)to notify the administrator via a mail.
Firstly, How do I 'trap' or 'read' any error that SQL Server 2000 would spit out( I don't have much experience using SQL OA procedures). And secondly, are there other ways to notify the administrators about a database going offline? The SQL mail notification hasn't worked for us as we run SQL Server on a cluster.
Any ideas?
Thanks
Firstly, How do I 'trap' or 'read' any error that SQL Server 2000 would spit out( I don't have much experience using SQL OA procedures). And secondly, are there other ways to notify the administrators about a database going offline? The SQL mail notification hasn't worked for us as we run SQL Server on a cluster.
Any ideas?
Thanks