• Call Toll Free: 1-855-909-3300

5 important log files in SQL Server 2005

Before discussing SQL Server log files, one must have the complete understanding of the transaction log in SQL server.

The Transaction Log

The transaction log in SQL server keeps track of all the transaction records and modifications made by each transaction in the database. The transaction log must be truncated on a regular basis so as to prevent it from filling up completely. However, monitoring log size is important because some log truncation can be delayed by some of the factors.

There are many other log files that help to diagnose and troubleshoot problems. Following log files plays an important role in SQL Server 2005.

Log File Viewer - SQL Server

  1. SQL Server Setup Log

The SQL Server 2005 Setup log, which is located at

%ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.

In case, the summary.txt log file shows a component failure, the root cause can be investigated by looking at the component’s log, which you’ll find in the

%Program-Files%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files directory.

  1. SQL Server Profiler Log

The primary application-tracing tool in SQL Server 2005is the SQL Server Profiler, which traces the system’s current activity in the database and stores it to a file for later analysis.

The Profiler logs are located in the

%ProgramFiles%\Microsoft SQL Server\MSSQL.1\MSSQL\LOG in the log.trc file directory.

5 important log files in SQL Server 2005-2

  1. SQL Server Agent Log

SQL Server Agent is a job scheduling subsystem in SQL Server 2005.It maintains the complete details about the jobs running on the server with the help of a set of log files.

These log files are located in the

%ProgramFiles%\Microsoft SQL Server\MSSQL.1\MSSQL\LOG directory.

Nine SQL Server Agent error log files are maintained by the SQL Server.  The current log file is named SQLAGENT .OUT, whereas archived files are sequentially numbered.

SQL Server Agent logs can be viewed by using SQL Server Management Studio (SSMS). Expand a server node, expand Management, click SQL Server Logs, and select the check box for SQL Server Agent.

  1. Windows Event Log

The Windows Event log is an important source of information for troubleshooting SQL Server errors. It contains three useful logs. Events in SQL Server and SQL Server Agent are recorded by the application log Agent and can be used by SQL Server Integration Services (SSIS) packages.

The security log records authentication information, and the system log records service startup and shutdown information. The Windows Event log can be viewed to Administrative Tools, Event Viewer.

5 important log files in SQL Server 2005

  1. SQL Server Error Log

The most important log file is used to troubleshoot system problems is the Error Log. Backups of the previous six logs are retained by the SQL Server, naming each archived log file sequentially. The current error log file is named ERRORLOG.

The error log can be viewed in the

%Program-Files%\Microsoft SQL Server\MSSQL.1MSSQL\LOG\ERRORLOG directory.

Open SSMS, expand a server node, expand Management, and then click SQL Server Logs.

Tagged under:

One thought on “5 important log files in SQL Server 2005”

Leave a Reply

Techarex NetWorks Products