February 18, 2004 at 9:43 pm
How to notify DBA of a SQL Server hang situation with out physically monitoring the server
February 20, 2004 at 5:49 am
use 2nd computer to periodically run a small query like "select @@servername" If you get timeout, other error, or no result then send your alert.
While this was no so uncommon in SQL6.5, we haven't ever seen a SQL2000 server "hang," closest thing to this was lost TCP/IP stack once. But we've seen the server appear to be unresponsive, due to massive blocking--if this is your problem then your check query needs either to more closely simulate actual user queries, or else check for blocking directly.
February 20, 2004 at 6:33 am
I use a purchased monitoring tool. Since I provide remote support for a site willing to pay for just a few hours a week of DBA coverage, they purchased SQLServer DiagnosticManager from NetIQ. It was easy to set up and I can basically ignore their system until I am notified about a problem. Takes a little time to know when you can ignore some messages because of other things going on in the environment but it has worked great. Try a free trial to see if it works for you.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply