Today’s post is a short and simple one. No system is error free. The key is in providing easy and efficient mechanisms to capture these errors and enabling the users of the system to extract meaningful information from these error logs.
Microsoft SQL Server logs certain system events and user-defined events to both - the SQL Server error log and the Microsoft Windows application log. Here is what MSDN has to say about SQL Server error logs:
“View the SQL Server error log to ensure that processes have completed successfully (for example, backup and restore operations, batch commands, or other scripts and processes). This can be helpful to detect any current or potential problem areas, including automatic recovery messages (particularly if an instance of SQL Server has been stopped and restarted), kernel messages, or other server-level error messages.”
Every time the SQL Server instance is started, a new SQL Server error log is created. The default number of logs that the SQL Server will collect before recycling the logs is 6. A user can customize the Error log limit from SSMS by following the steps outlined below:
Until we meet next time,
Be courteous. Drive responsibly.
Tweet to @nakulv_sql