5 important log files in SQL Server 2005
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.
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.
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.
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.
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.
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.
- Julia is Techarex Network’s Content Marketing Associate for Intuit products. She has worked as a B2B and Marketing Strategist for the last seven years, helping businesses with software implementation for Customer Service, CRM, and Email Marketing. Julia thrives in helping companies find the right software solution for their projects. Aside from his obvious passion for Marketing, Julia admits to being a foodie and travel enthusiast.
- SharePoint Hosting2018.02.20How to select the best between Cloud-based SharePoint and On-Premise SharePoint?
- MS Office2018.02.19Top 7 Reasons for SMBs to Get Managed Microsoft Office 365 Services
- QuickBooks2017.12.04Understanding the Nitty-Gritty of Collaborative Accounting
- QuickBooks2017.11.30Key Considerations Before You Convert Your Existing Company File for QuickBooks 2018