Determine which version and edition of SQL Server Database Engine is running

This article describes the procedures to determine the version and edition of SQL Server Database Engine is running.

Original product version:   SQL Server
Original KB number:   321185

To determine the version of SQL Server, you can use any of the following methods.

Note

The version information follows major.minor.build.revision pattern. The "revision" information is not typically used when checking version of SQL Server.

  • Method 1: Connect to the server by using Object Explorer in SQL Server Management Studio. After Object Explorer is connected, it will show the version information in parentheses, together with the user name that is used to connect to the specific instance of SQL Server.

  • Method 2: Look at the first few lines of the Errorlog file for that instance. By default, the error log is located at Program Files\Microsoft SQL Server\MSSQL.n\MSSQL\LOG\ERRORLOG and ERRORLOG.n files. The entries may resemble the following one:

    2011-03-27 22:31:33.50 Server Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64)
    March 29 2009 10:11:52
    Copyright (c) 1988-2008 Microsoft Corporation
    Express Edition (64-bit)
    on Windows NT 6.1 <X64> (Build 7600: )
    

    This entry provides all the necessary information about the product, such as version, product level, 64-bit versus 32-bit, the edition of SQL Server, and the OS version on which SQL Server is running.

    Note

    The output of this query has been enhanced to show additional information, as documented in the blog post article, What build of SQL Server are you using?, for the following versions:

    • SQL Server 2014 RTM CU10 and later versions
    • SQL Server 2014 Service Pack 1 CU3 and later versions
    • SQL Server 2012 Service Pack 2 CU7 and later versions
  • Method 3: Connect to the instance of SQL Server, and then run the following query:

    Select @@version
    

    An example of the output of this query is the following:

    Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64)
    March 29 2009 10:11:52
    Copyright (c) 1988-2008 Microsoft Corporation Express Edition (64-bit)
    on Windows NT 6.1 <X64> (Build 7600: )
    

    Note

    The output of this query has been enhanced to show additional information. This is documented in the blog post article, What build of SQL Server are you using?, for the following versions:

    • SQL Server 2014 RTM CU10 and later versions
    • SQL Server 2014 Service Pack 1 CU3 and later versions
    • SQL Server 2012 Service Pack 2 CU7 and later versions

    Screenshot of an example of enhanced output for SQL Server 2012 Service Pack 2 CU7. (SP2-CU7) is added in the first row.

  • Method 4: Connect to the instance of SQL Server, and then run the following query in SQL Server Management Studio (SSMS):

    SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')
    

    Note

    This query works for any instance of SQL Server 2000 or a later version.

    The following results are returned:

    • The product version (for example, 10.0.1600.22)
    • The product level (for example, RTM)
    • The edition (for example, Enterprise)

    For example, the results resemble the following.

    product version product level edition
    14.0.2027.2 RTM Developer Edition (64-bit)

    Note

  • Method 5: Starting in SQL Server 2008, you can also use the Installed SQL Server Features Discovery report. This report can be found by locating the Tools page of SQL Server Installation Center. This tool gives information about all the instances of SQL Server that are installed on the system. These include client tools such as SQL Server Management Studio. The only thing to be aware of is that this tool can be run locally only on the system where SQL Server is installed. It can't be used to obtain information about remote servers. For more information, see Validate a SQL Server Installation.

    A snapshot of a sample report is as follows:

    Screenshot shows a sample SQL Server 2016 Setup Discovery report.

See also