Locating the SQL Server logs directory is often the first critical step when diagnosing unexpected behavior, performance degradation, or service failures. Administrators frequently need to access these records to troubleshoot connectivity issues, identify failed login attempts, or analyze long-running queries. The exact path is not universal, however, as it depends heavily on the SQL Server version, instance name, and configuration parameters set during installation. Understanding the default structure and knowing how to query the active location is an essential skill for any database professional.
Default Log File Locations by Version
For a standard default instance without custom configuration, the SQL Server error log follows a predictable pattern based on the operating system drive. Historically, this path has remained consistent to ensure backward compatibility for scripting and manual navigation. Below is a breakdown of the typical directories for recent Windows Server versions.
SQL Server Version | Error Log Path
SQL Server 2019 and 2022 | C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\Log
SQL Server 2017 | C:\Program Files\Microsoft SQL Server\MSSQL14.MSSQLSERVER\MSSQL\Log
SQL Server 2016 | C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Log
SQL Server 2014 | C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log
Decoding the Instance Naming Convention
The number in the path (such as MSSQL15 or MSSQL14) corresponds to the major version year, while the instance name follows the version identifier. For a named instance called "SQLDEV", the path would adjust to reflect the instance directory. The logs for that named instance would reside in a folder specific to that configuration, preventing conflicts with other instances on the same server.
When dealing with the default instance, the directory name uses "MSSQLSERVER" as the instance ID. This is why you will never see "MSSQL15.MSSQLSERVER" listed as a named instance; it is simply the default. If you are working with a virtual machine provided by another team, it is wise to verify the instance name rather than assuming the directory structure.
Finding the Current Path Using T-SQL
Relying on documentation or file explorer can lead to mistakes if the server was installed with non-standard options. The most reliable method to determine the exact location is to query the SQL Server error log configuration directly from the database engine. Executing a simple system stored procedure returns the current path without requiring access to the file system.
Execute the following T-SQL command in SQL Server Management Studio (SSMS) to retrieve the error log file location:
EXEC xp_readerrorlog 0, 1; The result set will display the path to the currently active error log. This is particularly useful if the SQL Server service was restarted and the logs rolled over, as the active file name will change numerically (e.g., errorlog.1, errorlog.2).
