Determining the specific edition of your SQL Server installation is essential for understanding feature availability, licensing compliance, and performance capabilities. Whether you are troubleshooting a licensing issue, planning a feature rollout, or auditing your environment, knowing the exact version and edition provides clarity. This guide walks through multiple reliable methods to check SQL edition, ensuring you can verify the information regardless of your access level.
Using SQL Server Management Studio (SSMS)
For users with graphical interface access, SQL Server Management Studio offers the most straightforward approach. Once connected to the target instance, the server properties provide a direct answer without requiring additional queries.
Steps to View Server Properties
Open SQL Server Management Studio and establish a connection to the desired database engine.
Right-click the server name in the Object Explorer pane.
Select "Properties" from the context menu.
Navigate to the "General" page, where the "Edition" property displays the specific product version, such as "Enterprise" or "Standard".
Executing T-SQL Queries
When graphical tools are unavailable, or when scripting is required, Transact-SQL commands offer a precise programmatic method. These queries are valuable for automation and remote execution via command line utilities.
SERVERPROPERTY Function
The most direct T-SQL method utilizes the SERVERPROPERTY function. Running the following query returns the exact edition name as configured on the instance:
SELECT SERVERPROPERTY('Edition') AS SQL_Server_Edition; Additionally, the ProductLevel property indicates whether the instance is running a RTM, SP, or CU build, while ProductVersion returns the internal version number for deeper diagnostics.
Checking via Command Line
Administrators managing servers without GUI access can rely on the command prompt. The sqlcmd utility allows you to execute the same queries directly in the terminal, returning text-based results ideal for logging.
Open Command Prompt or PowerShell.
Connect to the SQL Server instance using the command: sqlcmd -S YourServerName -E .
Enter the T-SQL query to check SQL edition.
Press Enter to view the results directly in the console window.
Reviewing the Error Log
Another often-overlooked source of truth is the SQL Server error log. During the startup sequence, the instance logs detailed initialization messages, including the specific edition and licensing details. This method is particularly useful when the connection is experiencing authentication issues.
You can view the error log directly from SSMS by navigating to the "Management" node and selecting "SQL Server Logs," or by using the sp_readerrorlog stored procedure to filter for the edition string programmatically.
Using PowerShell
PowerShell provides a robust alternative for environment scanning, especially in large infrastructures where consistency is key. The `Get-SqlServer` cmdlet or direct WMI queries can retrieve the edition property across multiple servers simultaneously.
Cmdlets allow for filtering and exporting results to CSV files, making it simple to generate compliance reports. This approach is ideal for auditing environments to ensure that Enterprise or Standard editions are deployed according to architectural standards.
Verifying Licensing and Core Count
While identifying the edition is the primary goal, understanding the associated licensing model is equally important. The physical or virtual core count must align with the rules of the specific edition you are running.
