Link to home
Start Free TrialLog in
Avatar of ArtDecker
ArtDecker

asked on

How to create an alert that monitors event 17126 (SQL Server is ready for client connections) that works

We schedule weekly database server reboots.   I've created two alerts....one to trap error 17147 that does notify the approprate operator (me)...and the other for error 17126 (SQL Server is ready for client connections).   The 17126 alert gets written to the windows event log...but the alert never 'fires' notifying the operator.    I think that this is a timing issue in that upon a server restart,  the agent is just not running when the event occurs.    Since the SQL Server agent is dependent on the MSSQLSERVER agent...I can't start it first.    

I tried forwarding the events to a different but the results are the same.

Cany anyone help?

Art
Avatar of EugeneZ
EugeneZ
Flag of United States of America image

What version\ed\SP of MS SQL do you have?
Check for lates SP if you did not install one

also read - it can help :
http://databasejournal.com/features/mssql/article.php/3081171
Avatar of ArtDecker
ArtDecker

ASKER

SP3+ (v8.0.818)

Checked out the referenced article.   I don't fully understand the item that states 'Verify that the counter value is maintained for at least 20 seconds.   Is that an OS setting or something that I can do in the db.

Perhaps I don't fully understand the dependencies between the agent and the db.  I know I can't stop the database without stopping the agent.   Does the agent shutdown before the database does?  If so,  I would imagine that the database needs to be fully 'up' before the agent starts.   In that case,  my problem would appear to be a timing issue.   The database 'fires' the 17126 event before the agent is fully up to recognize the alert.  Would that make sense?   Would maintaining the counter value for a longer period help that.

Art

ASKER CERTIFIED SOLUTION
Avatar of EugeneZ
EugeneZ
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
to get info about MSSQL service status use windows utilities to get it from Event viewer logs about it