Locating the SQL Server error log is often the first critical step in diagnosing unexpected shutdowns, startup failures, or unusual behavior within your database environment. By default, the primary log file records significant events, including startup and shutdown messages, server errors, and warnings, providing a chronological trail for troubleshooting. Understanding the precise path for your specific installation is essential, as configurations can vary based on the version, edition, and how the instance was deployed. This guide details the methods to identify these log files efficiently, ensuring you can access vital diagnostic information without delay.
Default Log File Location by Version
The physical location of the logs adheres to a consistent structure across modern versions of the platform, typically nested within the main installation directory. This standardization applies to SQL Server 2012, 2014, 2016, 2017, 2019, and 2022, whether running on Windows Server or Linux containers. The path generally follows a pattern that includes the installation root, the specific version number, and a dedicated folder for instance-specific data. Knowing this default structure allows administrators to navigate directly to the directory when other configuration methods are unavailable.
Typical Path for Windows Instances
For a default instance on a Windows machine, the error log is usually stored under the `MSSQL` directory, specifically within the `Log` folder of the instance name. If you are working with a named instance, the path will include the instance identifier to segregate the files correctly. This hierarchical organization ensures that logs for different instances remain isolated, preventing confusion in multi-instance environments. You can typically find them at a location resembling the following structure.
Typical Path for Linux Deployments
On Linux systems, the structure aligns with the Filesystem Hierarchy Standard (FHS), placing application logs in a more centralized location. The error logs are generally found within the data directory specific to the instance, or within the standard logging folder managed by the systemd service. The exact path depends on whether you used the default data directory or specified a custom location during the initial configuration. Common locations include:
/var/opt/mssql/log/errorlog
/var/log/mssql/mssql-server/errorlog
Retrieving the Path via SQL Server Management Studio
Perhaps the most reliable method to determine the exact location is to query the instance directly using SQL Server Management Studio (SSMS). This approach bypasses the need to navigate the file system manually and retrieves the active path from the SQL Server error log configuration itself. By executing a specific system stored procedure, you can return the current startup parameters and log paths dynamically, ensuring you are viewing the accurate, live configuration.
Using the xp_readerrorlog Command
The `xp_readerrorlog` extended stored procedure provides immediate access to the contents of the error log. While it is commonly used to read log entries, executing it without parameters returns the primary log file path. This dynamic management view effectively reports the location of the current error log and the SQL Agent log, offering a real-time snapshot of the logging infrastructure. To use this method, follow these steps:
Open SQL Server Management Studio and connect to your target instance.
