SQL Server Error Log - Keep It Clean
The SQL Server Error Log and Windows Event Log are essential for trouble shooting some problems. But what do you do if there are a load of errors and warnings not related to your problem? You could spend hours researching issues that have nothing at all to do with your problem.This was brought home to me recently on a server that kept dropping user connections. The logs contained errors and warnings about Kerberos authentication, Perflib, SQL Browser, and the Cluster Service. It took longer than it should to identify the cause of the connection issue because it was not obvious which errors to follow up.
So when (if?) you have a quiet period, use it to clean up your logs. Look for errors or warnings and take the necessary action to prevent them from occurring. You'll find it much easier to resolve a serious problem when it occurs.
There is a section in this site for common errors and their resolutions. If you know of an error that is not included, you can get in touch with me through the contact me page.
Not found what you're looking for?
Use this search box. It is tuned for SQL Server searches. Try it and see!Do you have a question about SQL Server? Would you like to answer a question?
Go to the SQL FAQ to get started.
