Skip to content Skip to sidebar Skip to footer
Home / how to tell what version of sql server is running

how to tell what version of sql server is running

Post a Comment
Skip to main content

Determine the version, edition, and update level of SQL Server and its components

  • Article
  • 31 minutes to read

This commodity lists various builds or updates that are bachelor for unlike versions of SQL Server and describe the procedures to determine the version of SQL Server that is running on a given organization.

Original product version: SQL Server
Original KB number: 321185

Summary

  • A downloadable version of an Excel workbook that contains all the build versions together with their current back up lifecycle phase for 2005 through the electric current version is available. Click to download this Excel file now. (File name: SQL Server Builds V3.xlsx)

  • To learn what a specific version number of SQL Server maps to, or to find the KB commodity information for a specific cumulative update packet or a service pack, search for the version number in the SQL Server Complete Version listing tables.

  • To find the edition of your SQL Server case, you tin can use one of the procedures in Method ii through Method 5 in the Determine which version and edition of SQL Server Database Engine is running section.

    Annotation

    The version information and edition information are in the same output string.

Latest updates available for currently supported versions of SQL Server

Each of the following links provides data for all of the applicable products and technologies.

Version Latest Service Pack Latest German democratic republic Latest cumulative update Complete version information General Guidance
SQL Server 2019 None Gdr (15.0.2080.9 - January, 2021) CU15 for 2022 (15.0.4198.2 - January 2022)
CU8 + German democratic republic (15.0.4083.2 - Jan 2021)		 SQL Server 2022 builds SQL Server 2022 Installation
SQL Server 2017 None GDR (fourteen.0.2037.ii - January, 2021) CU29 for 2022 (fourteen.0.3436.1 - March 2022)
CU22 + Gdr (14.0.3370.1 - Jan 2021)		 SQL Server 2022 builds SQL Server 2022 Installation
SQL Server 2016 SP3 (13.0.6300.2 - September 2021)
SP2 (thirteen.0.5026.0 - Apr 2018)
SP1 (xiii.0.4001.0 - November 2016)		 Gdr for SP2 (13.0.5103.half dozen - January, 2021)
GDR for SP1 (13.0.4259.0 - July, 2019)
GDR for RTM (13.0.1745.2 - January, 2018)		 CU17 for 2022 SP2 (13.0.5888.11 - March 2021)
CU15 + GDR for SP2 (13.0.5865.1 - January 2021)
CU15 + GDR for SP1 (13.0.4604.0 - July 2019)
CU15 for SP1 (13.0.4574.0 - May 2019)
CU14 for SP2 (xiii.0.5830.85- August 2020)
CU9 for RTM (xiii.0.2216.0 - Nov 2017)		 SQL Server 2022 builds SQL Server 2022 Installation
SQL Server 2014 SP3 (12.0.6024.0 - October 2018)
SP2 (12.0.5000.0 - July 2016)
SP1 (12.0.4100.one - May 2015)		 GDR for SP3 (12.0.6164.21 - January, 2021)
GDR for SP2 (12.0.5223.6 - Jan, 2019)
GDR for SP1 (Baronial, 2017)
MS 15-058 (July, 2015)		 CU4 + GDR for SP3 (12.0.6433.1 - January 2021)
CU4 for SP3 (12.0.6329.1 - July 2019)
CU18 for SP2 (12.0.5687.1 - July 2019)
CU13 for SP1 (12.0.4522.0 - Baronial 2017)		 SQL Server 2022 builds SQL Server 2022 Installation
SQL Server 2012 SP4 (eleven.0.7001.0 - September 2017)
SP3 (eleven.0.6020.0 - Nov 2015)
SP2 (11.0.5058.0 - June 2014)
SP1 (xi.0.3000.00 - November 2012		 German democratic republic for SP4 (11.0.7507.2 - Jan, 2021)
GDR for SP3 (January, 2018)
MS 16-136 (November, 2016)
MS fifteen-058 (December, 2015)		 CU10 for SP3 (11.0.6607.3 - Baronial 2017)
CU16 for SP2 (11.0.5678.0 - January 2017)
CU16 for SP1 (11.0.3487.0 - May 2015)		 SQL Server 2012 builds SQL Server 2012 Installation
SQL Server 2008 R2 SP3 (10.50.6000.34 - September 2014)
SP2 (10.50.4000.0 - July 2012)		 GDR for SP3 (January, 2018)
MS xv-058 (July, 2015)		 None SQL Server 2008 R2 builds SQL Server 2008 R2 SP3 Installation
SQL Server 2008 SP4 (10.0.6000.29 - September 2014)
SP3 (x.00.5500.00 - October, 2011)		 Gdr for SP4 (January, 2018)
MS 15-058 (July, 2015)		 None SQL Server 2008 builds SQL Server 2008 Servicing

Note

"Latest" = During the past 12 months

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

To determine the version of SQL Server, you tin use whatsoever of the post-obit methods.

  • Method ane: Connect to the server past using Object Explorer in SQL Server Direction Studio. Subsequently Object Explorer is connected, it will evidence the version information in parentheses, together with the user name that is used to connect to the specific case of SQL Server.

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

                      2011-03-27 22:31:33.l Server Microsoft SQL Server 2008 (SP1) - ten.0.2531.0 (X64)   March 29 2009 10:11:52   Copyright (c) 1988-2008 Microsoft Corporation   Express Edition (64-bit)   on Windows NT vi.1 <X64> (Build 7600: )

    This entry provides all the necessary information most the product, such equally 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 prove additional information, every bit documented in the blog post commodity, What build of SQL Server are you using?, for the following versions:

    • SQL Server 2022 RTM CU10 and later on versions
    • SQL Server 2022 Service Pack 1 CU3 and afterwards versions
    • SQL Server 2012 Service Pack ii CU7 and later versions

  • Method iii: Connect to the instance of SQL Server, and then run the post-obit query:

                      Select @@version

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

                      Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64)   March 29 2009 10:eleven: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 web log mail article, What build of SQL Server are you using?, for the post-obit versions:

    • SQL Server 2022 RTM CU10 and later versions

    • SQL Server 2022 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 four: Connect to the case of SQL Server, and and then run the post-obit query in SQL Server Management Studio (SSMS):

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

    Notation

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

    The following results are returned:

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

    For example, the results resemble the post-obit.

    production version product level edition
    14.0.2027.ii RTM Developer Edition (64-bit)

  • Method 5: Starting in SQL Server 2008, you tin can also use the Installed SQL Server Features Discovery report. This report can be constitute by locating the Tools page of SQL Server Installation Heart. This tool gives data about all the instances of SQL Server that are installed on the organization. These include client tools such as SQL Server Direction Studio. The only thing to be enlightened of is that this tool can be run locally but on the organisation where SQL server is installed. It cannot be used to obtain data about remote servers. For more than information, see Validate a SQL Server Installation.

    A snapshot of a sample report is as follows:

    Screenshot shows a sample SQL Server 2022 Setup Discovery report.

  • SQL Server Management Studio (SSMS)

    To determine which versions of the customer tools are installed on your organisation, start Management Studio, and so click About on the Help menu. (See the following screenshot.)

    Screenshot of the About Microsoft SQL Server Management Studio window, which shows the versions of the client tools.

    Starting with SQL Server 2016, SQL Server management studio is offered every bit a carve up download. For additional data about various versions of the tool, review Release notes for SQL Server Management Studio (SSMS).

    SQL Server Data Tools

    For additional information virtually SQL Server Data Tools, review Download SQL Server Data Tools (SSDT) for Visual Studio.

SQL Server Reporting Services

The version of SQL Server Reporting Services (SSRS) is displayed on the Reporting Services Web Service URL, for example: http://servername/reportserver. The version is as well displayed in the Reporting Services Configuration tool.

SQL Server Integration Services

The version of SQL Server Integration Services aligns with the version of SQL server that you had installed.

SQL Server Assay Services

To determine the version of SQL Server Analysis Services, use one of the following methods:

  • Method 1: Connect to the server by using Object Explorer in SQL Server Management Studio. After Object Explorer is continued, it will show the version information in parentheses, together with the user proper noun that is used to connect to the specific case of Assay Services.

  • Method 2: Check the version of the Msmdsrv.exe file in the Assay Services bin binder. The default locations are shown in the following tabular array.

    Assay Services version Location
    2019 %ProgramFiles%\Microsoft SQL Server\MSAS15.InstanceName\OLAP\Bin\MSMDSrv.exe
    2017 %ProgramFiles%\Microsoft SQL Server\MSAS14.InstanceName\OLAP\Bin\MSMDSrv.exe
    2016 %ProgramFiles%\Microsoft SQL Server\MSAS13.InstanceName\OLAP\Bin\MSMDSrv.exe
    2014 %ProgramFiles%\Microsoft SQL Server\MSAS12.InstanceName\OLAP\Bin\MSMDSrv.exe
    2012 %ProgramFiles%\Microsoft SQL Server\MSAS11.InstanceName\OLAP\Bin\MSMDSrv.exe

  • Method 3: Utilize the registry subkeys that are listed in the post-obit table.

    Analysis Services version Location
    2019 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSAS15.InstanceName\MSSQLServer\CurrentVersion Key: CurrentVersion

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSAS15.InstanceName \Setup Keys: PatchLevel , Version, Primal Edition

    2017 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSAS14.InstanceName\MSSQLServer\CurrentVersion Primal: CurrentVersion

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSAS14.InstanceName \Setup Keys: PatchLevel , Version, Primal Edition

    2016 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSAS13.InstanceName\MSSQLServer\CurrentVersion Central: CurrentVersion

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSAS13.InstanceName \Setup Keys: PatchLevel , Version, Cardinal Edition

    2014 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSAS12.InstanceName\MSSQLServer\CurrentVersion Fundamental: CurrentVersion

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSAS12.InstanceName \MSSQLServer\CurrentVersion Key: CurrentVersion

    2012 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSAS11.InstanceName\MSSQLServer\CurrentVersion Key: CurrentVersion

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSAS11.InstanceName \Setup Keys: PatchLevel , Version, Central Edition

    For more information about verifying Assay Services build versions review Verify Analysis Services cumulative update build version.

SQL Server replication

Because replication agents may exist installed on several dissimilar computers, it is important to cheque the installed versions on all affected computers.

For instance, the Distribution Agent in Transactional or Peer-to-Peer replication may exist on computers that differ from the publisher instance of SQL Server and may exist on the various subscriber instances of SQL Server in a pull subscription.

If you use Spider web Synchronization for Merge Replication, the IIS web server may not exist the same computer as the computer that is running SQL Server. Therefore, you have replication agent files that are installed on the IIS web server. And y'all may take to bank check the version of those .dll files in the IIS virtual directory and update them explicitly to obtain the latest service packs, cumulative updates, and hotfixes for your web agents.

For more data, see Upgrade or patch replicated databases.

Full-text search

Full-text search components include the following:

  • Sqlserver.exe
  • Sql_fulltext_keyfile.dll
  • Iftsph.dll
  • Fd.dll
  • Fdhost.exe
  • Fdlauncher.exe

Except for Sqlservr.exe, these components may not be updated with each cumulative update or service pack for the respective SQL Server product. The versions of these files will change only when in that location is a fix to the respective component. Generally, y'all can check the file version of each of these .dll files. The highest version in the list is the version of the full-text search component that is installed on the system.

Y'all can use one of the following methods to determine the version of the full-text search component that is installed on your system.

Note

Each of these methods may betoken that the version of the full-text search component is either RTM or a version that is earlier than the current version of the database component. We admit that this is a trouble and are working on fixing it in a future update.

  • Method 1: Check the version of SQL Server Full-Text Key (Sql_fulltext_keyfile.dll) in the SQL Server 2008 R2 or SQL Server 2008 installation binder. Typically, for SQL Server 2008 R2, this file is located in the following folder:

    %ProgramFiles%\Microsoft SQL Server\MSQL10_50.\<Instance Proper name>\MSSQL

    For SQL Server 2008, this file typically is located in the following folder:

    %ProgramFiles%\Microsoft SQL Server\MSQL10.\<Case Proper noun>\MSSQL

  • Method 2: Check the following registry subkey:

    HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft sql server\Mssql10_50.instname\Setup\SQL_FULLTEXT_ADV

    An case entry at this registry subkey is the following:

                      featurelist: SQL_FullText_Adv=three SQL_FullText_CNI=3 ProductCode: {9DFA5914-C275-42E0-810E-C88E46A7F9EA} Patchlevel: ten.50.1765.0 Version: ten.50.1600.1

    In this instance entry, the tertiary line (Patchlevel) indicates the current build of full-text search component that is installed, and the fourth line (Version) normally shows the original version of total-text search that is installed. In this example, it is SQL Server 2008 R2.

  • Method three: Use the Summary.txt file that is created during setup. For SQL Server 2008 R2 and after versions, this file is located in the post-obit folder:

    %ProgramFiles%\Microsoft SQL Server\<nnn>\Setup Bootstrap\LOG\Summary.txt

    For values of <nnn> that correlate to your version review File Locations for Default and Named Instances of SQL Server.

    For SQL Server 2008, this file is located in the following binder:

    %ProgramFiles%\Microsoft SQL Server\100\Setup Bootstrap\LOG\Summary.txt

SQL Server Master Data Services (MDS)

The MDS Configuration Manager does non show the currently installed version number directly.

Be aware that MDS has a unique versioning scenario in which the SQL Server database engine installation does not necessarily match the MDS version. The version may vary when y'all compare the SQL Server installation to the binaries deployed in the MDS website and the MDS catalog schema version. Manual steps that use the MDS Configuration Managing director tool are required to update and to upgrade the MDS websites and database schemas. You can refer to the post-obit weblog mail on hotfix and service pack update methodology for MDS: Downloading and Installing SQL Server 2008 R2 Master Data Services (MDS) Cumulative Updates

The following registry subkey shows the binary versions that are installed on the SQL Server. Even so, this version does not necessarily match the website and database schema version until the MDS upgrade process is complete.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Master Data Services 10.5\CurrentVersion

You can bank check the installed product version and schema version by using the following query in the MDS catalog:

              select * from mds.mdm.tblSystem

SQL Server Native Client

Note

The major SQL Server version of latest SQL Server Native Customer is SQL Server 2012. It's uniform with SQL Server 2022 and SQL Server 2016. For additional information review Installing SQL Server Native Client.

To determine the version of SQL Server Native Client, use 1 of the following methods:

  • Method one: On the organisation where you lot want to find the version of Native Client, commencement the ODBC Administrator (odbcad32.exe), and so bank check the Version cavalcade under the Drivers tab.

  • Method 2: Check the post-obit PatchLevel or Version keys at the following registry locations.

    SQL version /
    SQL Server Native Client version    		 Registry subkeys
    SQL Server 2012, SQL Server 2022 and SQL Server 2016/ SQL Server Native Client 11.0 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SQLNCLI11\CurrentVersion
    SQL Server 2008 & SQL Server 2008 R2/
    SQL Server Native Client ten    		 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SQLNCLI10\CurrentVersion
    SQL Server 2005/
    SQL Server Native Client 9    		 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Native Client\CurrentVersion

SQL Server Browser

The browser version should friction match the highest version of the SQL Server Database Engine and of the instances of Assay Services that are installed on the computer.

SQL Server Author

To decide the version of SQL Server Writer, check the following registry subkey value:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SqlWriter\CurrentVersion Keys: PatchLevel or Version

Microsoft .NET Framework

To determine the version of .NET Framework on your system, see Determine which versions and service pack levels of .NET Framework are installed.

For more than information, meet Agreement the .NET Framework requirements for various versions of SQL Server.

SQL Azure

To find the version of your case of SQL Azure and related information, see the following topic in Books Online: SERVERPROPERTY (Transact-SQL).

SQL Server CE

To find the version of your example of SQL Server CE and related information, run across SQL Server CE previous versions documentation.

PolyBase

PolyBase for SQL Server on Windows

To discover the version of PolyBase and its related features in Windows, try the post-obit methods:

  • If the PolyBase service is running, run the following PowerShell script:
              Get-Process mpdwsvc -FileVersionInfo | Format-Tabular array -AutoSize
  • If the PolyBase service is not running or can't be started, run the post-obit PowerShell script:
              cd 'C:\Programme Files\Microsoft SQL Server' ls mpdwsvc.exe -r -ea silentlycontinue | % versioninfo | Format-Tabular array -AutoSize

PolyBase for SQL Server on Linux

To find the version of PolyBase installed and its related features in Ubuntu, try the following methods:

              apt listing mssql-server-polybase apt list mssql-server-polybase-hadoop

To find the version of PolyBase installed and its related features in RHEL, attempt the following methods:

              yum info mssql-server-polybase yum info mssql-server-polybase-hadoop                          
              yum list installed *polybase*

Windows or Linux

Alternatively, try the SQL Server Setup steps in this next department. To observe the version of PolyBase and its related features, refer to a fresh discovery report that runs inside the SQL Server Setup tools.

In Windows or Linux, find the installation folder \Setup Bootstrap\Log. The Summary.txt file shows a discovery written report of all features and versions. Nonetheless, if the near recent setup action was to add PolyBase to an existing SQL Server instance, the Summary.txt file volition not contain the PolyBase feature. This is because the discovery study volition have run before the PolyBase characteristic was added.

We recommend that yous refresh the Summary.txt report by running the features discovery report from SQL Server Setup. For more data, come across Validate a SQL Server Installation.

Machine Learning services

For Windows servers, refer to the CAB file versions which modify with SQL Server cumulative updates. Refer to the Rlauncher.config or PythonLauncher.config files in the Program Files\Microsoft SQL Server\MSSQL.nn\MSSQL\Binn directory to find the RHOME or PYTHONHOME binder locations of the CAB files. For the CAB versions that are included with SQL Server CU versions, see CAB downloads for offline installation of cumulative updates for SQL Server Machine Learning Services.

For Linux servers, the following command returns a listing of all mssql-specific installed packages, together with their version numbers:

              apt-get list --installed | --grep mssql

The version number of the mssql-server-extensibility package version is the SQL Server version of the Machine Learning Services characteristic.

The version number of the mssql-mlservices-packages-r or mssql-mlservices-packages-py refers to each linguistic communication package file. For more information, see Install SQL Server Machine Learning Services on Linux (Offline installation).

Frequently asked questions

Q1: How exercise you determine the version of SQL Server when SQL Server is not running?

A1: You can make up one's mind the version of SQL Server by using either Method 2 or Method 5 (for SQL Server 2008 and later versions) in the Determine which version and edition of SQL Server Database Engine is running] section of this commodity.

Q2: How exercise I map the product versions to product names?

A2: You tin utilize the following table every bit a reference.

Version pattern SQL Product
15.0.x.10 SQL Server 2019
14.0.x.x SQL Server 2017
xiii.0.x.10 SQL Server 2016
12.0.x.x SQL Server 2014
eleven.0.x.x SQL Server 2012
x.50.x.x SQL Server 2008 R2
10.00.10.x SQL Server 2008
ix.00.10.ten SQL Server 2005
eight.00.x.x SQL Server 2000

Frequently used terms and acronyms

Cumulative update (CU): A roll-up update that contains all previous critical on-demand hotfixes to date. Additionally, a CU contains fixes for issues that see the hotfix acceptance criteria. These criteria may include the availability of a workaround, the outcome on the client, the reproducibility of the problem, the complexity of the code that must be changed, and other topics.

Hotfix: A single, cumulative bundle that includes one or more files that are used to address a problem in a production and are cumulative at the binary and file level. A hotfix addresses a specific client situation and may not be distributed exterior the customer's organization.

RTM: Usually means "release to manufacturing". In the context of a product such equally SQL Server, it indicates that no service packs or hotfixes were applied to the product.

RTW: Usually means "release to web". It indicates a packet that was released to the spider web and made available to customers for downloading.

Service pack: A tested, cumulative gear up of all hotfixes, security updates, critical updates, and updates. Service packs may too incorporate boosted fixes for issues that are constitute internally since the release of the product and a limited number of client-requested design changes or features.

For more information, get to the following websites:

  • Announcing the Modern Servicing Model for SQL Server

  • Naming schema and Prepare expanse descriptions for SQL Server software update packages

  • Description of the standard terminology that is used to describe Microsoft software updates

  • Clarification of the standard terminology that is used to describe Microsoft software updates

  • An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems

  • Software release life cycle

  • SQL Server documentation

  • SQL Server product information center

  • SQL Server release blogs

SQL Server complete version list tables

Note

These tables use the following format and are ordered past the build number.

SQL Server 2019

Build number or version Service pack Update KB commodity Release date
15.0.4198.2 None CU15 5008996 January 27, 2022
15.0.4188.ii None CU14 5007182 November 22, 2021
15.0.4178.1 None CU13 5005679 October 05, 2021
15.0.4153.ane None CU12 5004524 August 04, 2021
15.0.4138.2 None CU11 5003249 June x, 2021
15.0.4123.ane None CU10 5001090 April 06, 2021
15.0.4102.2 None CU9 5000642 February eleven, 2021
15.0.4083.2 None CU8 + German democratic republic 4583459 January 12, 2021
xv.0.4073.23 None CU8 4577194 September 30, 2020
15.0.4063.15 None CU7 4570012 September 02, 2020
15.0.4053.23 None CU6 4563110 Baronial 04, 2020
xv.0.4043.sixteen None CU5 4552255 June 22, 2020
15.0.4033.1 None CU4 4548597 March 31, 2020
15.0.4023.6 None CU3 4538853 March 12, 2020
fifteen.0.4013.xl None CU2 4536075 February 13, 2020
15.0.4003.23 None CU1 4527376 January 07, 2020
fifteen.0.2070.41 None GDR1 4517790 Nov 04, 2019
xv.0.2000.5 None RTM NA November 04 2019

SQL Server 2017

Build number or version Service pack Update KB commodity Release date
xiv.0.3436.1 None CU29 5010786 March 30, 2022
fourteen.0.3430.2 None CU28 5008084 January 13, 2022
14.0.3421.10 None CU27 5006944 October 27, 2021
fourteen.0.3411.3 None CU26 5005226 September fourteen, 2021
14.0.3401.7 None CU25 5003830 July 12, 2021
14.0.3391.2 None CU24 5001228 May ten, 2021
14.0.3381.3 None CU23 5000685 February 24, 2021
14.0.3370.1 None CU22 + GDR 4583457 Jan 12, 2021
14.0.3356.20 None CU22 4577467 September 10, 2020
14.0.3335.seven None CU21 4557397 July 01, 2020
14.0.3294.2 None CU20 4541283 April 07, 2020
xiv.0.3281.6 None CU19 4535007 February 05, 2020
14.0.3257.three None CU18 4527377 December 09, 2019
fourteen.0.3238.1 None CU17 4515579 October 08, 2019
fourteen.0.3223.iii None CU16 4508218 Baronial 01, 2019
14.0.3192.2 None CU15 + GDR 4505225 July 09, 2019
14.0.3162.one None CU15 4498951 May 23, 2019
14.0.3103.1 None CU14 + Gdr 4494352 May fourteen, 2019
xiv.0.3076.i None CU14 4484710 March 25, 2019
14.0.3048.4 None CU13 4466404 December xviii, 2018
14.0.3045.24 None CU12 4464082 October 24, 2018
xiv.0.3038.14 None CU11 4462262 September xx, 2018
14.0.3037.ane None CU10 4342123 August 27, 2018
14.0.3035.2 None CU9 + GDR 4293805 August 14, 2018
fourteen.0.3030.27 None CU9 4341265 July 18, 2018
14.0.3029.xvi None CU8 4338363 June 21, 2018
xiv.0.3026.27 None CU7 4229789 May 23, 2018
fourteen.0.3025.34 None CU6 4101464 April 17, 2018
fourteen.0.3023.8 None CU5 4092643 March 20, 2018
fourteen.0.3022.28 None CU4 4056498 February twenty, 2018
14.0.3015.forty None CU3 4052987 Jan 04, 2018
14.0.3008.27 None CU2 4052574 Nov 28, 2017
14.0.3006.16 None CU1 4038634 October 24, 2017

SQL Server 2016

Build number or version Service pack Update KB article Release appointment
thirteen.0.6300.2 SP3 RTW/PCU3 5003279 September xv, 2021
13.0.5888.11 SP2 CU17 5001092 March 29, 2021
13.0.5882.1 SP2 CU16 5000645 February 11, 2021
13.0.5865.1 SP2 CU15 + Gdr 4583461 January 12, 2021
13.0.5850.fourteen SP2 CU15 4577775 September 28, 2020
13.0.5830.85 SP2 CU14 4564903 August 06, 2020
13.0.5820.21 SP2 CU13 4549825 May 28, 2020
13.0.5698.0 SP2 CU12 4536648 February 24, 2020
13.0.5598.27 SP2 CU11 4527378 Dec 09, 2019
13.0.5492.2 SP2 CU10 4524334 October 08, 2019
13.0.5426.0 SP2 CU8 4505830 July 31, 2019
13.0.5366.0 SP2 CU7 + Gdr 4505222 July 9, 2019
thirteen.0.5337.0 SP2 CU7 4495256 May 22, 2019
thirteen.0.5292.0 SP2 CU6 4488536 March xix, 2019
13.0.5264.i SP2 CU5 4475776 January 23, 2019
13.0.5233.0 SP2 CU4 4464106 November 13, 2018
13.0.5216.0 SP2 CU3 4458871 September 20, 2018
13.0.5201.2 SP2 CU2 + Security Update 4458621 August 21 2018
13.0.5153.0 SP2 CU2 4340355 July 16 2018
xiii.0.5149.0 SP2 CU1 4135048 May 30, 2018
xiii.0.5026.0 SP2 RTW/PCU2 4052908 Apr 24, 2018
thirteen.0.4604.0 SP1 CU15 + Gdr 4505221 July nine, 2019
thirteen.0.4574.0 SP1 CU15 4495257 May 16, 2019
13.0.4560.0 SP1 CU14 4488535 March xix, 2019
13.0.4550.1 SP1 CU13 4475775 January 23, 2019
thirteen.0.4541.0 SP1 CU12 4464343 November 13, 2018
13.0.4528.0 SP1 CU11 4459676 September 17, 2018
13.0.4224.16 SP1 CU10 + Security Update 4458842 Baronial 22, 2018
13.0.4514.0 SP1 CU10 4341569 July 16, 2018
thirteen.0.4502.0 SP1 CU9 4100997 May 30, 2018
thirteen.0.4474.0 SP1 CU8 4077064 March 19, 2018
xiii.0.4466.iv SP1 CU7 4057119 January 04, 2018
13.0.4457.0 SP1 CU6 4037354 November 20, 2017
xiii.0.4451.0 SP1 CU5 4040714 September xviii, 2017
thirteen.0.4446.0 SP1 CU4 4024305 August eight, 2017
xiii.0.4435.0 SP1 CU3 4019916 May fifteen, 2017
13.0.4422.0 SP1 CU2 4013106 March xx, 2017
13.0.4411.0 SP1 CU1 3208177 January 17, 2017
13.0.4001.0 SP1 RTW/PCU1 3182545 November 16, 2016
13.0.2216.0 RTM CU9 4037357 November 20, 2017
13.0.2213.0 RTM CU8 4040713 September 18, 2017
xiii.0.2210.0 RTM CU7 4024304 August 8, 2017
thirteen.0.2204.0 RTM CU6 4019914 May 15, 2017
xiii.0.2197.0 RTM CU5 4013105 March 20, 2017
thirteen.0.2193.0 RTM CU4 3205052 Jan 17, 2017
13.0.2186.half dozen RTM CU3 3205413 November 16, 2016
13.0.2164.0 RTM CU2 3182270 September 22, 2016
xiii.0.2149.0 RTM CU1 3164674 July 25, 2016

SQL Server 2014

Build number or version Service pack Update KB article Release date
12.0.6329.one SP3 CU4 4500181 July 29, 2019
12.0.6293.0 SP3 CU3 + GDR 4505422 July 9, 2019
12.0.6259.0 SP3 CU3 4491539 April 16, 2019
12.0.6214.1 SP3 CU2 4482960 Feb 19, 2019
12.0.6205.one SP3 CU1 4470220 December 12, 2018
12.0.6024.0 SP3 RTW/PCU3 4022619 October 30, 2018
12.0.5687.one SP2 CU18 4500180 July 29, 2019
12.0.5659.i SP2 CU17 + GDR 4505419 July nine, 2019
12.0.5632.1 SP2 CU17 4491540 April 16, 2019
12.0.5626.1 SP2 CU16 4482967 February xix, 2019
12.0.5605.1 SP2 CU15 4469137 December 12, 2018
12.0.5600.i SP2 CU14 4459860 October 15, 2018
12.0.5590.ane SP2 CU13 4456287 August 27, 2018
12.0.5589.7 SP2 CU12 4130489 June 18, 2018
12.0.5579.0 SP2 CU11 4077063 March nineteen, 2018
12.0.5571.0 SP2 CU10 4052725 January 16, 2018
12.0.5563.0 SP2 CU9 4055557 December eighteen, 2017
12.0.5557.0 SP2 CU8 4037356 Oct 16, 2017
12.0.5556.0 SP2 CU7 4032541 August 28, 2017
12.0.5553.0 SP2 CU6 4019094 August 8, 2017
12.0.5546.0 SP2 CU5 4013098 April 17, 2017
12.0.5540.0 SP2 CU4 4010394 Feb 21, 2017
12.0.5538.0 SP2 CU3 3204388 Dec 19, 2016
12.0.5522.0 SP2 CU2 3188778 October 17, 2016
12.0.5511.0 SP2 CU1 3178925 August 25, 2016
12.0.5000.0 SP2 RTW/PCU2 3171021 July 11, 2016
12.0.4522.0 SP1 CU13 4019099 Baronial 8, 2017
12.0.4511.0 SP1 CU12 4017793 April 17, 2017
12.0.4502.0 SP1 CU11 4010392 February 21, 2017
12.0.4491.0 SP1 CU10 3204399 December nineteen, 2016
12.0.4474.0 SP1 CU9 3186964 Oct 17, 2016
12.0.4468.0 SP1 CU8 3174038 Baronial fifteen, 2016
12.0.4459.0 SP1 CU7 3162659 June 20, 2016
12.0.4457.0 SP1 CU6 3167392 May 30,2016
12.0.4449.0 SP1 CU6 3144524 April 18, 2016
12.0.4438.0 SP1 CU5 3130926 February 22, 2016
12.0.4436.0 SP1 CU4 3106660 December 21, 2015
12.0.4427.24 SP1 CU3 3094221 Oct 19, 2015
12.0.4422.0 SP1 CU2 3075950 August 17, 2015
12.0.4416.0 SP1 CU1 3067839 June 19, 2015
12.0.4213.0 SP1 MS15-058: German democratic republic Security Update 3070446 July 14, 2015
12.0.4100.ane SP1 RTW/PCU1 3058865 May 04, 2015
12.0.2569.0 RTM CU14 3158271 June 20, 2016
12.0.2568.0 RTM CU13 3144517 April 18, 2016
12.0.2564.0 RTM CU12 3130923 February 22, 2016
12.0.2560.0 RTM CU11 3106659 December 21, 2015
12.0.2556.iv RTM CU10 3094220 October xix, 2015
12.0.2553.0 RTM CU9 3075949 August 17, 2015
12.0.2548.0 RTM MS15-058: QFE Security Update 3045323 July fourteen, 2015
12.0.2546.0 RTM CU8 3067836 June 19, 2015
12.0.2495.0 RTM CU7 3046038 April 20, 2015
12.0.2480.0 RTM CU6 3031047 February 16, 2015
12.0.2456.0 RTM CU5 3011055 Dec 17, 2014
12.0.2430.0 RTM CU4 2999197 October 21, 2014
12.0.2402.0 RTM CU3 2984923 Baronial eighteen, 2014
12.0.2381.0 RTM MS14-044: QFE Security Update 2977316 August 12, 2014
12.0.2370.0 RTM CU2 2967546 Fri, June 27, 2014
12.0.2342.0 RTM CU1 2931693 April 21, 2014
12.0.2269.0 RTM MS15-058: German democratic republic Security Update 3045324 July 14, 2015
12.0.2254.0 RTM MS14-044: GDR Security Update 2977315 Baronial 12, 2014
12.0.2000.viii RTM April 01, 2014

SQL Server 2012

Build number or version Service pack Update KB article Release date
eleven.0.7001.0 SP4 RTW/PCU4 4018073 October ii, 2017
11.0.6607.three SP3 CU10 4025925 August 8, 2017
11.0.6598.0 SP3 CU9 4016762 May xv, 2017
eleven.0.6594.0 SP3 CU8 4013104 March 20, 2017
11.0.6579.0 SP3 CU7 3205051 January 17, 2017
11.0.6567.0 SP3 CU6 3194992 Nov 17, 2016
eleven.0.6248.0 SP3 MS16-136 GDR Security Update 3194721 November viii, 2016
eleven.0.6544.0 SP3 CU5 3180915 September 19, 2016
eleven.0.6540.0 SP3 CU4 3165264 July 18, 2016
11.0.6537.0 SP3 CU3 3152635 May 16, 2016
eleven.0.6523.0 SP3 CU2 3137746 March 21,2016
11.0.6518.0 SP3 CU1 3123299 January 19, 2016
eleven.0.6020.0 SP3 RTW/PCU3 3072779 Nov twenty, 2015
11.0.5678.0 SP2 CU16 3205054 November 17, 2016
xi.0.5676.0 SP2 CU15 3205416 November 17, 2016
11.0.5657.0 SP2 CU14 3180914 September 19, 2016
xi.0.5655.0 SP2 CU13 3165266 July 18, 2016
11.0.5649.0 SP2 CU12 3152637 May 16, 2016
11.0.5646.0 SP2 CU11 3137745 March 21,2016
11.0.5644.2 SP2 CU10 3120313 January 19, 2016
11.0.5641.0 SP2 CU9 3098512 Nov 16, 2015
11.0.5634.i SP2 CU8 3082561 September 21, 2015
xi.0.5623.0 SP2 CU7 3072100 July 20, 2015
11.0.5613.0 SP2 MS15-058: QFE Security Update 3045319 July 14, 2015
11.0.5592.0 SP2 CU6 3052468 May xviii, 2015
11.0.5582.0 SP2 CU5 3037255 March 16, 2015
11.0.5569.0 SP2 CU4 3007556 January 19, 2015
11.0.5556.0 SP2 CU3 3002049 November 17, 2014
11.0.5548.0 SP2 CU2 2983175 September xv, 2014
11.0.5532.0 SP2 CU1 2976982 July 23, 2014
11.0.5343.0 SP2 MS15-058: GDR Security Update 3045321 July xiv, 2015
xi.0.5058.0 SP2 RTW/PCU2 2958429 June x, 2014
eleven.0.3513.0 SP1 MS15-058: QFE Security Update 3045317 July 14, 2015
eleven.0.3482.00 SP1 CU13 3002044 November 17, 2014
11.0.3470.00 SP1 CU12 2991533 September 15, 2014
11.0.3460.0 SP1 MS14-044: QFE Security Update 2977325 Baronial 12, 2014
11.0.3449.00 SP1 CU11 2975396 July 21, 2014
11.0.3431.00 SP1 CU10 2954099 May 19, 2014
11.0.3412.00 SP1 CU9 2931078 March 17, 2014
xi.0.3401.00 SP1 CU8 2917531 January 20, 2014
11.0.3393.00 SP1 CU7 2894115 November xviii, 2013
11.0.3381.00 SP1 CU6 2874879 September 16, 2013
11.0.3373.00 SP1 CU5 2861107 July 15, 2013
11.0.3368.00 SP1 CU4 2833645 May xxx, 2013
eleven.0.3349.00 SP1 CU3 2812412 March xviii, 2013
11.0.3339.00 SP1 CU2 2790947 January 21, 2013
11.0.3321.00 SP1 CU1 2765331 November 20, 2012
11.0.3156.00 SP1 MS15-058: GDR Security Update 3045318 July xiv, 2015
11.0.3153.00 SP1 MS14-044: Gdr Security Update 2977326 Baronial 12, 2014
11.0.3000.00 SP1 RTW/PCU1 2674319 November 7, 2012
11.0.2424.00 RTM CU11 2908007 December 16, 2013
xi.0.2420.00 RTM CU10 2891666 Oct 21, 2013
xi.0.2401.00 RTM CU6 2728897 February xviii, 2013
11.0.2395.00 RTM CU5 2777772 December 17, 2012
xi.0.2383.00 RTM CU4 2758687 October fifteen, 2012
eleven.0.2376.00 RTM MS12-070: QFE Security Update 2716441 Oct 9, 2012
11.0.2332.00 RTM CU3 2723749 August 31, 2012
11.0.2325.00 RTM CU2 2703275 June 18, 2012
xi.0.2316.00 RTM CU1 2679368 April 12, 2012
11.0.2218.00 RTM MS12-070: German democratic republic Security Update 2716442 October 9, 2012
11.0.2100.60 RTM March half dozen, 2012

SQL Server 2008 R2

Build number or version Service pack Update KB article Release engagement
10.50.6529.00 SP3 MS15-058: QFE Security Update 3045314 July 14, 2015
x.50.6220.00 SP3 MS15-058: QFE Security Update 3045316 July 14, 2015
10.fifty.6000.34 SP3 RTW/PCU3 2979597 September 26, 2014
10.50.4339.00 SP2 MS15-058: QFE Security Update 3045312 July 14, 2015
10.fifty.4321.00 SP2 MS14-044: QFE Security Update 2977319 August 14, 2014
x.50.4319.00 SP2 CU13 2967540 June thirty, 2014
10.l.4305.00 SP2 CU12 2938478 Apr 21, 2014
10.l.4302.00 SP2 CU11 2926028 February 18, 2014
10.50.4297.00 SP2 CU10 2908087 Dec 17, 2013
10.50.4295.00 SP2 CU9 2887606 October 28, 2013
10.50.4285.00 SP2 CU7 2844090 June 17, 2013
ten.50.4279.00 SP2 CU6 2830140 April 15, 2013
10.50.4276.00 SP2 CU5 2797460 February 18, 2013
10.50.4270.00 SP2 CU4 2777358 December 17, 2012
10.l.4266.00 SP2 CU3 2754552 October xv, 2012
10.l.4263.00 SP2 CU2 2740411 August 31, 2012
10.50.4260.00 SP2 CU1 2720425 July 24, 2012
10.50.4042.00 SP2 MS15-058: German democratic republic Security Update 3045313 July 14, 2015
x.50.4033.00 SP2 MS14-044: GDR Security Update 2977320 August 12, 2014
10.l.4000.0 SP2 RTW/PCU2 2630458 July 26, 2012
10.l.2881.00 SP1 CU14 2868244 August viii, 2013
10.50.2876.00 SP1 CU13 2855792 June 17, 2013
ten.50.2874.00 SP1 CU12 2828727 April 15, 2013
ten.l.2869.00 SP1 CU11 2812683 February 18, 2013
ten.l.2866.00 SP1 CU9 2756574 October 15, 2012
10.50.2861.00 SP1 MS12-070: QFE Security Update 2716439 Oct nine, 2012
10.50.2822.00 SP1 CU8 2723743 August 31, 2012
10.50.2817.00 SP1 CU7 2703282 June 18, 2012
ten.l.2811.00 SP1 CU6 2679367 April sixteen, 2012
x.50.2806.00 SP1 CU5 2659694 February 22, 2012
ten.50.2796.00 SP1 CU4 2633146 Dec nineteen, 2011
ten.50.2789.00 SP1 CU3 2591748 Oct 17, 2011
10.l.2772.00 SP1 CU2 2567714 August 15, 2011
10.fifty.2769.00 SP1 CU1 2544793 July 18, 2011
ten.fifty.2550.00 SP1 MS12-070: GDR Security Update 2754849 October 9, 2012
x.50.2500.0 SP1 RTW/PCU1 2528583 July 12, 2011
ten.50.1815.00 RTM CU13 2679366 Apr 16, 2012
10.l.1810.00 RTM CU12 2659692 February 21, 2012
10.l.1807.00 RTM CU10 2591746 October 17, 2011
10.l.1804.00 RTM CU9 2567713 August 15, 2011
10.50.1790.00 RTM MS11-049: QFE Security Update 2494086 June 14, 2011
x.l.1777.00 RTM CU7 2507770 April 18, 2011
10.fifty.1765.00 RTM CU6 2489376 Feb 21, 2011
10.fifty.1753.00 RTM CU5 2438347 Dec twenty, 2010
x.50.1746.00 RTM CU4 2345451 October 18, 2010
ten.fifty.1734.00 RTM CU3 2261464 August sixteen, 2010
10.50.1720.00 RTM CU2 2072493 June 21, 2010
10.50.1702.00 RTM CU1 981355 May 18, 2010
x.l.1617.00 RTM MS11-049: Gdr Security Update 2494088 June 14, 2011
10.fifty.1600.1 RTM May 10, 2010

SQL Server 2008

Build number or version Service pack Update KB article Release appointment
x.00.6535.00 SP3 MS15-058: QFE Security Update 3045308 July fourteen, 2015
10.00.6241.00 SP3 MS15-058: Gdr Security Update 3045311 July xiv, 2015
10.00.5890.00 SP3 MS15-058: QFE Security Update 3045303 July 14, 2015
10.00.5869.00 SP3 MS14-044: QFE Security Update 2984340, 2977322 August 12, 2014
10.00.5867.00 (on-demand update package) 2877204
ten.00.5861.00 SP3 CU17 2958696 May 19, 2014
x.00.5852.00 SP3 CU16 2936421 March 17, 2014
10.00.5850.00 SP3 CU15 2923520 Jan 20, 2014
x.00.5848.00 SP3 CU14 2893410 November 18, 2013
10.00.5846.00 SP3 CU13 2880350 September xvi, 2013
x.00.5844.00 SP3 CU12 2863205 July 15, 2013
ten.00.5840.00 SP3 CU11 2834048 May 20, 2013
10.00.5835.00 SP3 CU10 2814783 March 18, 2013
x.00.5829.00 SP3 CU9 2799883 January 21, 2013
x.00.5828.00 SP3 CU8 2771833 November nineteen, 2012
x.00.5826.00 SP3 MS12-070: QFE Security Update 2716435 October 9, 2012
10.00.5794.00 SP3 CU7 2738350 September 17, 2012
ten.00.5788.00 SP3 CU6 2715953 July sixteen, 2012
ten.00.5785.00 SP3 CU5 2696626 May 21, 2012
10.00.5768.00 SP3 CU2 2633143 Nov 21, 2011
10.00.5766.00 SP3 CU1 2617146 October 17, 2011
ten.00.5538.00 SP3 MS15-058: German democratic republic Security Update 3045305 July 14, 2015
10.00.5520.00 SP3 MS14-044: GDR Security Update 2977321 August 12, 2014
10.00.5512.00 SP3 MS12-070: GDR Security Update 2716436 October ix, 2012
ten.00.5500.00 SP3 RTW / PCU 3 2546951 Oct 6, 2011
10.00.4371.00 SP2 MS12-070: QFE Security Update 2716433 October 9, 2012
10.00.4332.00 SP2 CU10 2696625 May 21, 2012
10.00.4330.00 SP2 CU9 2673382 March xix, 2012
x.00.4326.00 SP2 CU8 2648096 January 16, 2012
10.00.4323.00 SP2 CU7 2617148 November 21, 2011
10.00.4321.00 SP2 CU6 2582285 September 19, 2011
10.00.4316.00 SP2 CU5 2555408 July 18, 2011
x.00.4311.00 SP2 MS11-049: QFE Security Update 2494094 June xiv, 2011
ten.00.4285.00 SP2 CU4 2527180 May 16, 2011
ten.00.4279.00 SP2 CU3 2498535 March 17, 2011
10.00.4266.00 SP2 CU1 2289254 November xv, 2010
10.00.4067.00 SP2 MS12-070: Gdr Security Update 2716434 October 9, 2012
10.00.4064.00 SP2 MS11-049: GDR Security Update 2494089 June 14, 2011
ten.00.4000.00 SP2 RTW / PCU 2 2285068 September 29, 2010
10.00.2850.0 SP1 CU16 2582282 September xix, 2011
ten.00.2847.0 SP1 CU15 2555406 July 18, 2011
x.00.2841.0 SP1 MS11-049: QFE Security Update 2494100 June 14, 2011
ten.00.2821.00 SP1 CU14 2527187 May 16, 2011
10.00.2816.00 SP1 CU13 2497673 March 17, 2011
10.00.2804.00 SP1 CU11 2413738 November 15, 2010
10.00.2775.00 SP1 CU8 981702 May 17, 2010
10.00.2746.00 SP1 CU5 975977 Nov 16, 2009
ten.00.2734.00 SP1 CU4 973602 September 21, 2009
x.00.2723.00 SP1 CU3 971491 July twenty, 2009
x.00.2714.00 SP1 CU2 970315 May 18, 2009
10.00.2710.00 SP1 CU1 969099 April 16, 2009
10.00.2573.00 SP1 MS11-049: GDR Security update 2494096 June xiv, 2011
ten.00.2531.00 SP1 RTW / PCU 1 Apr 2009
10.00.1835.00 RTM CU10 979064 March fifteen, 2010
10.00.1823.00 RTM CU8 975976 Nov sixteen, 2009
10.00.1787.00 RTM CU3 960484 Jan 19, 2009
10.00.1779.00 RTM CU2 958186 Nov nineteen, 2008
10.00.1763.00 RTM CU1 956717 September 22, 2008
10.00.1600.22 RTM August 6, 2008

SQL Server 2005

Build number or version Service pack Update KB article Release date
9.00.5324 SP4 MS12-070: QFE Security update 2716427 Oct ix, 2012
9.00.5292 SP4 MS11-049: QFE Security update 2494123 June xiv, 2011
9.00.5069 SP4 MS12-070: GDR Security update 2716429 October 9, 2012
nine.00.5057 SP4 MS11-049: GDR Security update 2494120 June 14, 2011
ix.00.5000 SP4 RTW / PCU4 December 16, 2010
9.00.4309 SP3 CU11 2258854 August 16, 2010
9.00.4305 SP3 CU10 983329 June 21, 2010
nine.00.4285 SP3 CU8 978915 February sixteen, 2010
9.00.4230 SP3 CU5 972511 Baronial 17, 2009
9.00.4226 SP3 CU4 970279 June 15, 2009
9.00.4211 SP3 CU2 961930 February xvi, 2009
9.00.4060 SP3 MS11-049: GDR Security update 2494113 June 14, 2011
9.00.4035 SP3 RTW 955706 Dec 15, 2008
9.00.3325 SP2 CU13 967908 April 20, 2009
ix.00.3282 SP2 CU9 953752 Baronial 18, 2008
nine.00.3257 SP2 CU8 951217 June 16, 2008
ix.00.3239 SP2 CU7 949095 April 14, 2008
9.00.3077 SP4 MS09-004: GDR Security update 960089 February 10, 2009
9.00.3042 SP2 937137
9.00.2047 SP1
9.00.1399 RTM

SQL Server 2000

Build number or version Version description, (KB number for that update), release date
8.00.2283 Post-SP4 hotfix for MS09-004 (971524)
8.00.2282 MS09-004: KB959420 October 29,2008
8.00.2273 MS08-040 - KB 948111 July eight, 2008
viii.00.2040 Post-SP4 AWE fix (899761)
8.00.2039 SQL Server 2000 SP4
eight.00.1007 Update.exe Hotfix Installer Baseline two (891640)
8.00.977 Update.exe Hotfix Installer Baseline 1 (884856)
8.00.818 (821277)
8.00.765 Post SP3 hotfix rollup
eight.00.760 SQL Server 2000 SP3 or SP3a (8.00.766 ssnetlib.dll)
8.00.701 Hotfix Installer v.1 released
8.00.534 SQL Server 2000 SP2
8.00.384 SQL Server 2000 SP1
8.00.194 SQL Server 2000 RTM or MSDE 2.0

Older versions of SQL Server

SQL Server 7.0

Use the version number in the post-obit tabular array to identify the production or service pack level.

Version number Service pack
7.00.1063 SQL Server 7.0 Service Pack 4
7.00.961 SQL Server 7.0 Service Pack 3
7.00.842 SQL Server 7.0 Service Pack 2
7.00.699 SQL Server 7.0 Service Pack i
7.00.623 SQL Server 7.0 RTM

SQL Server 6.5

Use the version number in the following table to identify the product or service pack level.

Version number Service pack
half-dozen.50.479 SQL Server vi.5 Service Pack 5a Update
six.fifty.416 SQL Server 6.5 Service Pack 5a
6.l.415 SQL Server 6.5 Service Pack five
vi.50.281 SQL Server 6.5 Service Pack iv
6.50.258 SQL Server 6.5 Service Pack iii
half dozen.l.240 SQL Server 6.5 Service Pack 2
vi.50.213 SQL Server 6.5 Service Pack 1
vi.50.201 SQL Server 6.5 RTM

thornellglight.blogspot.com

Source: https://docs.microsoft.com/en-us/troubleshoot/sql/general/determine-version-edition-update-level

You may like these posts

Post a Comment for "how to tell what version of sql server is running"