I am seeing these errors as well. Does that mean the error never fired if in the LAST OCCURRED column it says NEVER OCCURRED? This would be a good sign right? Company is on SQL 7 For the top msdb and tempdb erros they have an Error of 9002 Thanks

We had a similar error while running SQL2005SP2. We did receive an error 1067 when manually restarting it via the services snapin. Turns out dot net 2.0 was corrupted. This was only determined while trying to repair the SQL install and received a prompt regarding dot net 2.0. Nothing else in the event...

Welcome to the forum & SQL Server world! There are few articles on web to help you: http://www.databasejournal.com/features/mssql/article.php/1498781 http://www.sqlservercentral.com/columnists/lPeysakhovich/sqlserveralerts.asp http://www.mssqlcity.com/Articles/Adm/alert_troubleshooting.htm

MSDN article on adding and removing counters, this blog post too (hot from oven) . Follow this thread too and do not post multiple (duplicate) posts for the same problem.

I would second Trigger fashion in this case than running some sort of monitoring, as with trigger you could put a condition stating if beyond 49500 then alerting would help, also you could do with a job provided the SQLAgent has no issues in alerting.

There is no specified timeframe to say within x months you there will be a security update patch, but its worth check every month for such bulletin information from MSSecurity site. Also you have information over there about how to get notifications for such updates.