May 13, 2008 at 3:31 pm
Hi, there are about 9000 error message codes, in SQL 2000 the most critical were about 130 (Severity 20-25)
I will be using a monitoring app that will send alerts based on the SQL Error codes
In SQL 2005 what are the most critical errors to monitoring? I know that the answer depends on different scenarios, but let me know your experiences in real world scenarios.
Regards
May 13, 2008 at 4:29 pm
Hi
Please never only use the errorlog as a main monitoring component.
I suggest the following:
Review the SQL server 2000 operations guide (monitoring chapter) and familiarise yourself with monitoring. Remember most of us are problem resolvers not monitoring experts. :hehe:
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops0.mspx
PS: you can use the OPS guide for 2005 as well
Choose your monitoring product carefully - concentrate on pro-active monitoring and re-active monitoring products.
Look at products like Operations manager from MS system center 2007, include profiler or PSSDIAG .Query your system catalogs frequently - DMV's and DMF's. Know your DBCC commands, understand IO ....do not go and monitor unprepared then it will be a waste of time and you will have a abundance of data that you can do nothing with.
Just a tip as well ...decide on a monitoring team or individual that reports issues to the more oprational guys..this is a spesialized job espasially in a enterprise environement.
Know what you want to monitor and when ..it will all fall into place after that.
May 14, 2008 at 7:22 am
Thanks !
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply