Access this form by selecting
Server Logs in the
navigation pane,
selecting a file in the
object list, and clicking the open icon
.
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, and
so on.
A new error log is created each time an instance of SQL Server is started,
although the sp_cycle_errorlog system stored procedure can be used to cycle the
error log files without having to restart the instance of SQL Server. Typically,
SQL Server retains backups of the previous six logs and gives the most recent
log backup the extension .1, the second most recent the extension .2, and so on.
The current error log has no extension.