How to determine the version of SQL Server
How to determine the edition of SQL Server & its components
How to determine the service pack of SQL Server
This article describes how to determine your current Microsoft SQL Server version number and the corresponding product or service pack level. It also describes how to determine the specific edition of SQL Server that you are using.
Notes
- If you just need to know what a specific version number of SQL server maps to or the KB information for a specific cumulative update package or a service pack, refer to the More Information section of this article and search for the version number.
- If you just want to find the latest builds for SQL Server, you can refer to the following article. Or, you can check the tables that correspond to your product in the More Information section of this article.957826 Where to find information about the latest SQL Server builds
How to determine the version of SQL Server Client tools
SQL Server Management Studio (SSMS)
To determine the version of the client tools that are installed on your system, start Management Studio, and then clickAbout on the Help menu. (The screen shot for this step is listed below).
SQL Server Business Intelligence Development Studio (BIDS)
To check the version of Analysis Services Designer, of Integration Services Designer, or of SQL Server Reporting Services Designer, follow these steps:
- Under your SQL program group, start SQL Server Business Intelligence Development Studio.
- On the Help menu, click About.
- In the Installed products list, select the required component, and then notice the version that is given under theProduct details text box.
(The screen shot for this step is listed below).
SQL Server 2005 / Visual Studio 2005
SQL Server 2008 / SQL Server 2008 R2 / Visual Studio 2008
How to determine which version and edition of SQL Server Database Engine is running
To determine the version of SQL Server, you can use any of the following methods:
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:
As you can see, this entry gives 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.
Method 3: Connect to the instance of SQL Server, and then run the following query:
Method 4: Connect to the instance of SQL Server, and then run the following query:
The following results are returned:
For example, the results resemble the following.
Note The SERVERPROPERTY function returns individual properties that relate to the version information, although the@@VERSIONfunction combines the output into one string. If your application requires individual property strings, you can use the SERVERPROPERTY function to return them instead of parsing the @@VERSIONresults.
Method 5: Starting with 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 cannot be used to obtain information about remote servers. For more information, visit the following blog post on the Microsoft Developer Network (MSDN):
A snapshot of a sample report is as follows:
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:
2011-03-27 22:31:33.50 Server Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64) Mar 29 2009 10:11:52 Copyright (c) 1988-2008 Microsoft Corporation Express Edition (64-bit) on Windows NT 6.1(Build 7600: )
Method 3: Connect to the instance of SQL Server, and then run the following query:
Select @@versionAn example of the output of this query is as follows:
Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64) Mar 29 2009 10:11:52 Copyright (c) 1988-2008 Microsoft Corporation Express Edition (64-bit) on Windows NT 6.1(Build 7600: )
Method 4: Connect to the instance of SQL Server, and then run the following query:
SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')Note This query works with any instance of SQL Server 2000 or of 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.
10.0.1600.22 | RTM | Enterprise Edition |
Method 5: Starting with 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 cannot be used to obtain information about remote servers. For more information, visit the following blog post on the Microsoft Developer Network (MSDN):
A snapshot of a sample report is as follows:
SQL Server 2014 version information
The following table lists the major releases of SQL Server 2014.
For more information information about the latest service packs for SQL Server 2014, click the following article number to view the article in the Microsoft Knowledge Base:
Release | Product Version |
---|---|
SQL Server 2014 SP1 | 12.0.4100.1 |
SQL Server 2014 RTM | 12.0.2000.80 |
2958069 How to obtain the latest service pack for SQL Server 2014
For more information about the latest cumulative updates available for SQL Server 2014, click the following article number to view the article in the Microsoft Knowledge Base:
2936603 SQL Server 2014 build versions
SQL Server 2012 version information
The following table lists the major releases of SQL Server 2012.
For more information information about the latest service packs for SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:
Release | Product Version |
---|---|
SQL Server 2012 Service Pack 2 | 11.0.5058.0 |
SQL Server 2012 Service Pack 1 | 11.00.3000.00 |
SQL Server 2012 RTM | 11.00.2100.60 |
2755533 How to obtain the latest service pack for SQL Server 2012
For more information about the latest cumulative updates available for SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:
2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was released
2772858 The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released
2983249 The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 2 was released
SQL Server 2008 R2 version information
The following table lists the major releases of SQL Server 2008 R2.
For more information information about the latest service packs for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
For more information about the latest cumulative updates available for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
Release | Product version |
---|---|
SQL Server 2008 R2 Service Pack 3 | 10.50.6000.34 |
SQL Server 2008 R2 Service Pack 2 | 10.50.4000.0 |
SQL Server 2008 R2 Service Pack 1 | 10.50.2500.0 |
SQL Server 2008 R2 RTM | 10.50.1600.1 |
2527041 How to obtain the latest service pack for SQL Server 2008 R2
For more information about the latest cumulative updates available for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released
2567616 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released
2730301 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released
SQL Server 2008 version information
The following table lists the major releases of SQL Server 2008.
For more information information about the latest service packs for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
Release | Product version |
---|---|
SQL Server 2008 Service Pack 4 | 10.00.6000.29 |
SQL Server 2008 Service Pack 3 | 10.00.5500.00 |
SQL Server 2008 Service Pack 2 | 10.00.4000.00 |
SQL Server 2008 Service Pack 1 | 10.00.2531.00 |
SQL Server 2008 RTM | 10.00.1600.22 |
968382 How to obtain the latest service pack for SQL Server 2008
For more information about the latest cumulative updates available for SQL Server 2008, click the following article numbers to view the articles in the Microsoft Knowledge Base:
956909 The SQL Server 2008 builds that were released after SQL Server 2008 was released
970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
2402659 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released
2629969 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 3 was released
SQL Server 2005 version information
The following table lists the major releases of SQL Server 2005.
For more information information about the latest service packs for SQL Server 2005, click the following article number to view the article in the Microsoft Knowledge Base:
Release | Product version |
---|---|
SQL Server 2005 Service Pack 4 | 9.00.5000.00 |
SQL Server 2005 Service Pack 3 | 9.00.4035 |
SQL Server 2005 Service Pack 2 | 9.00.3042 |
SQL Server 2005 Service Pack 1 | 9.00.2047 |
SQL Server 2005 RTM | 9.00.1399 |
913089 How to obtain the latest service pack for SQL Server 2005
sFor more information about the latest cumulative updates available for SQL Server 2005, click the following article number to view the article in the Microsoft Knowledge Base:
937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
960598 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
2485757 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 4 was released
SQL Server 2000 version information
The following table lists version number of the Sqlservr.exe file.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
Release | Product version |
---|---|
SQL Server 2000 Service Pack 4 | 8.00.2039 |
SQL Server 2000 Service Pack 3 | 8.00.760 |
SQL Server 2000 Service Pack 2 | 8.00.534 |
SQL Server 2000 Service Pack 1 | 8.00.384 |
SQL Server 2000 RTM | 8.00.194 |
290211 How to obtain the latest SQL Server 2000 service pack
SQL Server Reporting Services
To determine the version of SQL Server Reporting Services, refer to the following topic in SQL Server Books Online:
SQL Server Integration Services
To determine the version of SQL Server Integration Services, refer to the following article in the Microsoft Knowledge Base:
942177 How to determine the version of SQL Server Integration Services
SQL Server Analysis 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 connected, it will show the version information in parentheses, together with the user name that is used to connect to the specific instance of Analysis Services.
Method 2: Check the version of the Msmdsrv.exe file in the Analysis Services bin folder. The default locations are shown in the following table.
Method 3: Use the registry keys that are listed in the following table.
For more information, visit the following Microsoft TechNet blog post:
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 Analysis Services.
Method 2: Check the version of the Msmdsrv.exe file in the Analysis Services bin folder. The default locations are shown in the following table.
Analysis Services version | Location |
---|---|
2008 R2 | C:\Program Files\Microsoft SQL Server\MSAS10_50.InstanceName\OLAP\bin\MsMdSrv.exe |
2008 | C:\Program Files\Microsoft SQL Server\MSAS10.InstanceName\OLAP\bin\MsMdSrv.exe |
2005 | C:\Program Files\Microsoft SQL Server\MSSQL.n\OLAP\Bin\MsMdSrv.exe |
2000 | C:\Program Files\Microsoft Analysis Services\Bin\MsMdSrv.exe |
Method 3: Use the registry keys that are listed in the following table.
Analysis Services version | Location |
---|---|
2008 R2 | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSAS10_50.InstanceName \MSSQLServer\CurrentVersion Key: CurrentVersion HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSAS10_50.InstanceName \Setup Keys: PatchLevel , Version, Key Edition |
2008 | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSAS10.InstanceName\MSSQLServer\CurrentVersion Key: CurrentVersion HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSAS10.InstanceName \Setup\ Keys: PatchLevel, Version, Edition |
2005 | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.#\MSSQLServer\CurrentVersion Key: CurrentVersoin HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.#\Setup Keys: PatchLevel, Version, Edition |
2000 | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLAP Server\CurrentVersion Key: CSDVersion HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLAP Server\Setup Key: PatchLevel |
For more information, visit the following Microsoft TechNet blog post:
SQL Server replication
Because replication agents may be installed on several different computers, it is important to check the installed versions on all affected computers.
For example, 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 Web Synchronization for Merge Replication or SQL Server 2000 Windows CE Edition replication, the IIS web server may not be 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 you may have to 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 information, see the following topic in SQL Server Books Online:
For example, 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 Web Synchronization for Merge Replication or SQL Server 2000 Windows CE Edition replication, the IIS web server may not be 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 you may have to 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 information, see the following topic in SQL Server Books Online:
Full-text search
Full-text search components include the following:
You 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 indicate that the version of the full-text search compnent is either RTM or a version that is earlier than the current version of the database component. We acknowledge that this is a problem 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 folder. Typically, for SQL Server 2008 R2, this file is located in the following folder:
For SQL Server 2008, this file typically is located in the following folder:
Method 2: Check the following registry subkey:
An example entry at this registry key is the following:
In this example entry, the third line (Patchlevel) indicates the current build of full-text search component that is installed, and the fourth line (Version) usually shows the original version of full-text search that is installed. In this case, it is SQL Server 2008 R2.
Method 3: Use the Summary.txt file that is created during setup. For SQL Server 2008 R2, this file is located in the following folder:
For SQL Server 2008, this file is located in the following folder:
See the following article in the Microsoft Knowledge Base for a known issue with full-text search components in SQL Server 2008 installations:
- Sqlserver.exe
- Sql_fulltext_keyfile.dll
- Iftsph.dll
- Fd.dll
- Fdhost.exe
- Fdlauncher.exe
You 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 indicate that the version of the full-text search compnent is either RTM or a version that is earlier than the current version of the database component. We acknowledge that this is a problem 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 folder. Typically, for SQL Server 2008 R2, this file is located in the following folder:
%ProgramFiles%\Microsoft SQL Server\MSQL10_50.\MSSQL
For SQL Server 2008, this file typically is located in the following folder:
%ProgramFiles%\Microsoft SQL Server\MSQL10.\MSSQL
Method 2: Check the following registry subkey:
HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft sql server\Mssql10_50.instname\Setup\SQL_FULLTEXT_ADV
featurelist: SQL_FullText_Adv=3 SQL_FullText_CNI=3ProductCode: {9DFA5914-C275-42E0-810E-C88E46A7F9EA}Patchlevel: 10.50.1765.0Version: 10.50.1600.1
Method 3: Use the Summary.txt file that is created during setup. For SQL Server 2008 R2, this file is located in the following folder:
%ProgramFiles%\Microsoft SQL Server\110\Setup Bootstrap\LOG\Summary.txt
For SQL Server 2008, this file is located in the following folder:
%ProgramFiles%\Microsoft SQL Server\100\Setup Bootstrap\LOG\Summary.txt
See the following article in the Microsoft Knowledge Base for a known issue with full-text search components in SQL Server 2008 installations:
973888 The Full-Text Search component is not completely rolled back to the Service Pack 1 version after you uninstall Cumulative Update 3 for SQL Server 2008 Service Pack 1 that is applied by using a slipstream installation
SQL Server Master Data Services (MDS)
The MDS Configuration Manager does not 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 you 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 Manager tool are required to update and to upgrade the MDS websites and database schemas. You can refer to the following blog post on hotfix and service pack update methodology for MDS:
The following registry key shows the binary versions that are installed on the SQL Server. However, this version does not necessarily match the website and database schema version until the MDS upgrade process is complete.
You can check the installed product version and schema version by using the following query in the MDS catalog:
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 you 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 Manager tool are required to update and to upgrade the MDS websites and database schemas. You can refer to the following blog post on hotfix and service pack update methodology for MDS:
The following registry key shows the binary versions that are installed on the SQL Server. However, 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 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
To determine the version of SQL Server Native Client, use one of the following methods:
Method 1: On the system where you want to find the version of Native Client, start the ODBC Administrator (odbcad32.exe), and then check the Version column under the Drivers tab.
Method 2: Check the following PatchLevel or Version keys at the following registry locations.
Method 1: On the system where you want to find the version of Native Client, start the ODBC Administrator (odbcad32.exe), and then check the Version column under the Drivers tab.
Method 2: Check the following PatchLevel or Version keys at the following registry locations.
SQL version / SQL Server Native Client version | Registry keys |
---|---|
SQL Server 2008 R2 | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SQLNCLI10\CurrentVersion |
SQL Server 2008 / SQL Server Native Client 10 | 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 2012 | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SQLNCLI11\CurrentVersion |
SQL Server Browser
The browser version should match the highest version of the SQL Server Database Engine and of the instances of Analysis Services that are installed on the computer.
SQL Server Writer
To determine the version of SQL Server Writer, check the following registry key value:
Keys: PatchLevel or Version
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SqlWriter\CurrentVersion
The Microsoft .NET Framework
To determine the version of the .NET Framework on your system, refer to the following article in the Microsoft Knowledge Base:
318785 How to determine which versions and service pack levels of the Microsoft .NET Framework are installed
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2027770 Understanding the .NET Framework requirements for various versions of SQL Server
SQL Azure
To find the version of your instance of SQL Azure and related information, see the following topic in Books Online:
SQL Server CE
To find the version of your instance of SQL Server CE and related information, see the following resources:
- SQL Server Compact Release Versions
- 325808 SQL Server 2000 Windows CE Edition component releases and versions
More information
Frequently asked questions
Q1: How do you determine the version of SQL Server when SQL Server is not running?
A1: You can determine the version of SQL Server by using either method 2 or method 5 (for SQL Server 2008 or later versions) in the "How to determine which version of SQL Server Database Engine is running" section of this article.
Q2: How do I map the product versions to product names?
A2: You can use the following table as a reference.
A1: You can determine the version of SQL Server by using either method 2 or method 5 (for SQL Server 2008 or later versions) in the "How to determine which version of SQL Server Database Engine is running" section of this article.
Q2: How do I map the product versions to product names?
A2: You can use the following table as a reference.
Version pattern | SQL Product |
---|---|
12.0.x.x | SQL Server 2014 |
11.0.x.x | SQL Server 2012 |
10.50.x.x | SQL Server 2008 R2 |
10.00.x.x | SQL Server 2008 |
9.00.x.x | SQL Server 2005 |
8.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 meet the hotfix acceptance criteria. These criteria may include the availability of a workaround, the effect on the customer, the reproducibility of the problem, the complexity of the code that must be changed, and other topics.
Hotfix: A single, cumulative package that includes one or more files that are used to address a problem in a product and are cumulative at the binary and file level. A hotfix addresses a specific customer situation and may not be distributed outside the customer's organization.
RTM: Usually means "release to manufacturing." In the context of a product such as SQL Server, it indicates that no service packs or hotfixes were applied to the product.
RTW: Usually means "release to web." It indicates a package that was released to the web and made available to customers for downloading.
Service pack: A tested, cumulative set of all hotfixes, security updates, critical updates, and updates. Service packs may also contain additional fixes for problems that are found internally since the release of the product and a limited number of customer-requested design changes or features.
For more information, visit the following websites:
Hotfix: A single, cumulative package that includes one or more files that are used to address a problem in a product and are cumulative at the binary and file level. A hotfix addresses a specific customer situation and may not be distributed outside the customer's organization.
RTM: Usually means "release to manufacturing." In the context of a product such as SQL Server, it indicates that no service packs or hotfixes were applied to the product.
RTW: Usually means "release to web." It indicates a package that was released to the web and made available to customers for downloading.
Service pack: A tested, cumulative set of all hotfixes, security updates, critical updates, and updates. Service packs may also contain additional fixes for problems that are found internally since the release of the product and a limited number of customer-requested design changes or features.
For more information, visit the following websites:
- 822499 Naming schema for Microsoft SQL Server software update packages
- 824684 Description of the standard terminology that is used to describe Microsoft software updates
- 935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
- http://en.wikipedia.org/wiki/Software_release_life_cycle
SQL Server common build numbers and service packs
Note These tables use the following format and are ordered by the build number.
Build number or version | Version description, (KB number for that update), release date |
---|
SQL Server 2014
Build number or version | Version description, (KB number for that update), release date |
---|---|
12.0.4422.0 | SP1 CU #2 (3075950) August 17, 2015 |
12.0.4416.1 | SP1 CU #1 (3067839) June 19, 2015 |
12.0.4100.1 | SP1 RTW/PCU 1(3058865) May 4, 2015 |
12.0.2553.0 | RTM CU #9 (3075949) August 17, 2015 |
12.0.2546.0 | RTM CU #8 (3067836) June 19, 2015 |
12.0.2495.0 | RTM CU #7 (3046038) April 20, 2015 |
12.0.2480.0 | RTM CU #6 (3031047) February 16, 2015 |
12.0.2456.0 | RTM CU #5 (3011055) December 17, 2014 |
12.0.2430.0 | RTM CU #4 (2999197) October 21, 2014 |
12.0.2402.0 | RTM CU #3 (2984923) August 18, 2014 |
12.0.2370.0 | RTM CU #2 (2967546) June 27, 2014 |
12.0.2342.0 | RTM CU #1 (2931693) April 21, 2014 |
12.0.2000.8 | RTM – April 1, 2014 |
SQL Server 2012
Build number or version | Version description, (KB number for that update), release date |
---|---|
11.0.5634.1 | SP2 CU #8 (3082561) September 21, 2015 |
11.0.5623.0 | SP2 CU #7 (3072100) July 20, 2015 |
11.0.5592.0 | SP2 CU #6 (3052468) May 18, 2015 |
11.0.5582.0 | SP2 CU #5 (3037255) March, 16, 2015 |
11.0.5569.0 | SP2 CU #4 (3007556) January 19, 2015 |
11.0.5556.0 | SP2 CU #3 (3002049) November 17, 2014 |
11.0.5548.0 | SP2 CU #2 (2983175) September 15, 2014 |
11.0.5532.0 | SP2 CU #1 (2976982) July 23, 2014 |
11.0.5058.0 | SP2 RTW/PCU 2(2958429), June 10, 2014 |
11.0.3482.00 | SP1 CU #13 (3002044) November 17, 2014 |
11.0.3470.00 | SP1 CU #12 (2991533) September 15, 2014 |
11.0.3449.00 | SP1 CU #11 (2975396) July 21, 2014 |
11.0.3431.00 | SP1 CU #10 (2954099) May 19, 2014 |
11.0.3412.00 | SP1 CU #9 (2931078) March 17, 2014 |
11.0.3401.00 | SP1 CU #8 (2917531) January 20, 2014 |
11.0.3393.00 | SP1 CU #7 (2894115) November 18, 2013 |
11.0.3381.00 | SP1 CU #6 (2874879) September 16, 2013 |
11.0.3373.00 | SP1 CU #5 (2861107) July 15, 2013 |
11.0.3368.00 | SP1 CU #4 (2833645) May 30, 2013 |
11.0.3349.00 | SP1 CU #3 (2812412) March 18, 2013 |
11.0.3339.00 | SP1 CU #2 (2790947) January 21, 2013 |
11.0.3321.00 | SP1 CU #1 (2765331) November 20, 2012 |
11.0.3000.00 | SP1 RTW/PCU 1(2674319), November 07, 2012 |
11.0.2424.00 | RTM CU #11 (2908007) December 16, 2013 |
11.0.2420.00 | RTM CU #10 (2891666) October 21, 2013 |
11.0.2419.00 | RTM CU #9 (2867319) August 20, 2013 |
11.0.2410.00 | RTM CU #8 (2844205) June 17, 2013 |
11.0.2405.00 | RTM CU #7 (2823247) April 15, 2013 |
11.0.2401.00 | RTM CU #6 (2728897) February 18, 2013 |
11.0.2395.00 | RTM CU #5 (2777772) Dec 17, 2012 |
11.0.2383.00 | RTM CU #4 (2758687) October 15, 2012 |
11.0.2332.00 | RTM CU #3 (2723749) August 31, 2012 |
11.0.2325.00 | RTM CU #2 (2703275) June 18, 2012 |
11.0.2316.00 | RTM CU #1 (2679368) April 12, 2012 |
11.0.2100.60 | RTM – March 6, 2012 |
SQL Server 2008 R2
Build number or version | Version description, (KB number for that update), release date |
---|---|
10.50.4319.00 | SP2 CU #13 (2967540) June 30, 2014 |
10.50.4305.00 | SP2 CU #12 (2938478) April 21, 2014 |
10.50.4302.00 | SP2 CU #11 (2926028) February 18, 2014 |
10.50.4297.00 | SP2 CU #10 (2908087) December 17, 2013 |
10.50.4295.00 | SP2 CU #9 (2887606) October 28, 2013 |
10.50.4290.00 | SP2 CU #8 (2871401) August 22, 2013 |
10.50.4285.00 | SP2 CU #7 (2844090) June 17, 2013 |
10.50.4279.00 | SP2 CU #6 (2830140) April 15, 2013 |
10.50.4276.00 | SP2 CU #5 (2797460) February 18, 2013 |
10.50.4270.00 | SP2 CU #4 (2777358) Dec 17, 2012 |
10.50.4266.00 | SP2 CU #3 (2754552) October 15, 2012 |
10.50.4263.00 | SP2 CU #2 (2740411) August 31, 2012 |
10.50.4260.00 | SP2 CU #1 (2720425) July 24, 2012 |
10.50.4000.0 | SP2 RTW/PCU 2(2630458), July 26, 2012 |
10.50.2881.00 | SP1 CU #14 (2868244) August 8, 2013 |
10.50.2876.00 | SP1 CU #13 (2855792) June 17, 2013 |
10.50.2874.00 | SP1 CU #12 (2828727) April 15, 2013 |
10.50.2869.00 | SP1 CU #11 (2812683) February 18, 2013 |
10.50.2868.00 | SP1 CU #10 (2783135) Dec 17, 2012 |
10.50.2866.00 | SP1 CU #9 (2756574) October 15, 2012 |
10.50.2822.00 | SP1 CU #8 (2723743) August 31, 2012 |
10.50.2817.00 | SP1 CU #7 (2703282) June 18, 2012 |
10.50.2811.00 | SP1 CU #6 (2679367) Apr 16, 2012 |
10.50.2806.00 | SP1 CU #5 (2659694) Feb 22, 2012 |
10.50.2796.00 | SP1 CU #4 (2633146) Dec 19, 2011 |
10.50.2789.00 | SP1 CU #3 (2591748) Oct 17, 2011 |
10.50.2772.00 | SP1 CU #2 (2567714) Aug 15, 2011 |
10.50.2769.00 | SP1 CU #1 (2544793) Jul 18, 2011 |
10.50.2500.0 | SP1 RTW/PCU 1(2528583), July 12, 2011 |
10.50.1815.00 | RTM CU #13 (2679366) Apr 16, 2012 |
10.50.1810.00 | RTM CU #12 (2659692) Feb 21, 2012 |
10.50.1809.00 | RTM CU #11 (2633145) Dec 19, 2011 |
10.50.1807.00 | RTM CU #10 (2591746) Oct 17, 2011 |
10.50.1804.00 | RTM CU #9 (2567713) Aug 15, 2011 |
10.50.1797.00 | RTM CU #8 (2534352) June 20, 2011 |
10.50.1777.00 | RTM CU #7 (2507770) Apr 18, 2011 |
10.50.1765.00 | RTM CU #6 (2489376) Feb 21, 2011 |
10.50.1753.00 | RTM CU #5 (2438347) Dec 20, 2010 |
10.50.1746.00 | RTM CU #4 (2345451) Oct 18, 2010 |
10.50.1734.00 | RTM CU #3 (2261464) Aug 16, 2010 |
10.50.1720.00 | RTM CU #2 (2072493) Jun 21, 2010 |
10.50.1702.00 | RTM CU #1 (981355) May 18, 2010 |
10.50.1617.00 | GDR Security Update (2494088), June 21, 2011 |
10.50.1600.1 | RTM – May 10, 2010 |
SQL Server 2008
Build number or version | Version description, (KB number for that update), release date |
---|---|
10.00.5850.00 | SP3 CU #15 (2923520) January 20, 2014 |
10.00.5848.00 | SP3 CU #14 (2893410) November 18, 2013 |
10.00.5846.00 | SP3 CU #13 (2880350) September 16, 2013 |
10.00.5844.00 | SP3 CU #12 (2863205) July 15, 2013 |
10.00.5840.00 | SP3 CU #11 (2834048) May 20, 2013 |
10.00.5835.00 | SP3 CU #10 (2814783) March 18, 2013 |
10.00.5829.00 | SP3 CU #9 (2799883) January 21, 2013 |
10.00.5828.00 | SP3 CU #8 (2771833) November 19, 2012 |
10.00.5794.00 | SP3 CU #7 (2738350) September 17, 2012 |
10.00.5788.00 | SP3 CU #6 (2715953) July 16, 2012 |
10.00.5785.00 | SP3 CU #5 (2696626) May 21, 2012 |
10.00.5775.00 | SP3 CU #4 (2673383) Mar 19, 2012 |
10.00.5770.00 | SP3 CU #3 (2648098) Jan 16, 2012 |
10.00.5768.00 | SP3 CU #2 (2633143) Nov 21, 2011 |
10.00.5766.00 | SP3 CU #1 (2617146) Oct 17, 2011 |
10.00.5500.00 | SP3 RTW / PCU 3 (2546951) Oct 6, 2011 |
10.00.4333.00 | SP2 CU #11 (2715951) July 16, 2012 |
10.00.4332.00 | SP2 CU #10 (2696625) May 21, 2012 |
10.00.4330.00 | SP2 CU #9 (2673382) Mar 19, 2012 |
10.00.4326.00 | SP2 CU #8 (2648096) Jan 16, 2012 |
10.00.4323.00 | SP2 CU #7 (2617148) Nov 21, 2011 |
10.00.4321.00 | SP2 CU #6 (2582285) Sep 19, 2011 |
10.00.4316.00 | SP2 CU #5 (2555408) Jul 18, 2011 |
10.00.4285.00 | SP2 CU #4 (2527180) May 16, 2011 |
10.00.4279.00 | SP2 CU #3 (2498535) Mar 17, 2011 |
10.00.4272.00 | SP2 CU #2 (2467239) Jan 17, 2011 |
10.00.4266.00 | SP2 CU #1 ( 2289254) Nov 15, 2010 |
10.00.4064.00 | GDR Security Update (2494089), June 14, 2011 |
10.00.4000.00 | SP2 RTW / PCU 2 (2285068) Sep 29, 2010 |
10.00.2850.0 | SP1 CU #16 (2582282) Sep 19, 2011 |
10.00.2847.0 | SP1 CU #15 (2555406) Jul 18, 2011 |
10.00.2821.00 | SP1 CU #14 (2527187) May 16, 2011 |
10.00.2816.00 | SP1 CU #13 (2497673) Mar 17, 2011 |
10.00.2808.00 | SP1 CU #12 (2467236) Jan 17, 2011 |
10.00.2804.00 | SP1 CU #11 (2413738) Nov 15, 2010 |
10.00.2799.00 | SP1 CU #10 (2279604) Sep 20, 2010 |
10.00.2789.00 | SP1 CU #9 (2083921) July 19, 2010 |
10.00.2775.00 | SP1 CU #8 (981702) May 17, 2010 |
10.00.2766.00 | SP1 CU #7 (979065) Mar 26, 2010 |
10.00.2757.00 | SP1 CU #6 (977443) Jan 18, 2010 |
10.00.2746.00 | SP1 CU #5 (975977) Nov 16, 2009 |
10.00.2734.00 | SP1 CU #4 (973602) Sep 21, 2009 |
10.00.2723.00 | SP1 CU #3 (971491) Jul 20, 2009 |
10.00.2714.00 | SP1 CU #2 (970315) May 18, 2009 |
10.00.2710.00 | SP1 CU #1 (969099) Apr 16, 2009 |
10.00.2573.00 | GDR Security update (2494096), June 14, 2011 |
10.00.2531.00 | SP1 RTW / PCU 1 April, 2009 |
10.00.1835.00 | RTM CU #10 (979064) Mar 15, 2010 |
10.00.1828.00 | RTM CU #9 (977444) Jan 18, 2010 |
10.00.1823.00 | RTM CU #8 (975976) Nov 16, 2009 |
10.00.1818.00 | RTM CU #7 (973601) Sep 21, 2009 |
10.00.1812.00 | RTM CU #6 (971490) Jul 20, 2009 |
10.00.1806.00 | RTM CU #5 (969531) May 18, 2009 SP1 |
10.00.1798.00 | RTM CU #4 (963036) Mar 16, 2009 |
10.00.1787.00 | RTM CU #3 (960484) Jan 19, 2009 |
10.00.1779.00 | RTM CU #2 (958186) Nov 19, 2008 |
10.00.1763.00 | RTM CU #1 (956717) Sept 22, 2008 |
10.00.1600.22 | RTM – Aug 6, 2008 |
SQL Server 2005
Build number or version | Version description, (KB number for that update), release date |
---|---|
9.00.5266 | SP4 CU #3 (2507769) Mar 22, 2011 |
9.00.5259 | SP4 CU #2 (2489409) Feb 21, 2010 |
9.00.5254 | SP4 CU #1 (2464079) Dec 23, 2010 |
9.00.5000 | SP4 RTW (PCU4) Dec 16, 2010 |
9.00.4325 | SP3 CU #15 (2507766) Mar 22 , 2011 |
9.00.4317 | SP3 CU #14 (2489375) Feb 21, 2011 |
9.00.4315 | SP3 CU #13 (2438344) Dec 20, 2010 |
9.00.4311 | SP3 CU #12 (2345449) Oct 18, 2010SP3 |
9.00.4309 | SP3 CU #11 (2258854) Aug 16, 2010 |
9.00.4305 | SP3 CU #10 (983329) Jun 21, 2010 |
9.00.4294 | SP3 CU #9 (980176) Apr 19, 2010 |
9.00.4285 | SP3 CU #8 (978915) Feb 16, 2010 |
9.00.4273 | SP3 CU #7 (976951) Dec 21, 2009 |
9.00.4266 | SP3 CU #6 (974648) Oct 19, 2009 |
9.00.4230 | SP3 CU #5 (972511) Aug 17, 2009 |
9.00.4226 | SP3 CU #4 (970279) June 15, 2009 |
9.00.4220 | SP3 CU #3 (967909) Apr 20, 2009 |
9.00.4211 | SP3 CU #2 (961930) Feb 16, 2009 |
9.00.4207 | SP3 CU #1 (959195) Dec 19, 2008 |
9.00.4053 | Security update (970892) Oct 12, 2009 |
9.00.4035 | SP3 RTW (955706) Dec 15, 2008 |
9.00.3356 | SP2 CU #17 (976952) Dec 21, 2009 |
9.00.3355 | SP2 CU #16 (974647) Oct 19, 2009 |
9.00.3330 | SP2 CU #15 (972510) Aug 17, 2009 |
9.00.3328 | SP2 CU #14 (970278) June 15, 2009 |
9.00.3325 | SP2 CU #13 (967908) Apr 20, 2009 |
9.00.3315 | SP2 CU #12 (960485) Feb 16, 2009 |
9.00.3301 | SP2 CU #11 (958735) Dec 15, 2008 |
9.00.3294 | SP2 CU #10 (956854) Oct 21, 2008 |
9.00.3282 | SP2 CU #9 (953752) Aug 18, 2008 |
9.00.3257 | SP2 CU #8 (951217) Jun 16, 2008 |
9.00.3239 | SP2 CU #7 (949095) Apr 14, 2008 |
9.00.3228 | SP2 CU #6 (946608) Feb 18, 2008 |
9.00.3215 | SP2 CU #5 (943656) Dec 17, 2007 |
9.00.3200 | SP2 CU #4 (941450) Oct 15, 2007 |
9.00.3186 | SP2 CU #3 (939537) Aug 20, 2007 |
9.00.3175 | SP2 CU #2 (936305) June 18, 2007 |
9.00.3161 | SP2 CU #1 (935356) April 16, 2007 |
9.00.3152 | SP2 Rollup (933097) May 15, 2007 |
9.00.3068 | Security update (948109) Jul 8, 2008 |
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 8, 2008 |
8.00.2040 | Post-SP4 AWE fix (899761) |
8.00.2039 | SQL Server 2000 SP4 |
8.00.1007 | Update.exe Hotfix Installer Baseline 2 (891640) |
8.00.977 | Update.exe Hotfix Installer Baseline 1 (884856) |
8.00.818 | (821277) |
8.00.765 | Post SP3 hotfix rollup |
8.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 following table to identify the product 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 1 |
7.00.623 | SQL Server 7.0 RTM |
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
301511 How to obtain the latest SQL Server 7.0 service pack
SQL Server 6.5
Use the version number in the following table to identify the product or service pack level.Version number | Service pack |
---|---|
6.50.479 | SQL Server 6.5 Service Pack 5a Update |
6.50.416 | SQL Server 6.5 Service Pack 5a |
6.50.415 | SQL Server 6.5 Service Pack 5 |
6.50.281 | SQL Server 6.5 Service Pack 4 |
6.50.258 | SQL Server 6.5 Service Pack 3 |
6.50.240 | SQL Server 6.5 Service Pack 2 |
6.50.213 | SQL Server 6.5 Service Pack 1 |
6.50.201 | SQL Server 6.5 RTM |
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
273914 Readme.txt for SQL Server 6.5 post-Service Pack 5a Update
Properties
Article ID: 321185 - Last Review: 09/22/2015 02:29:00 - Revision: 67.0
- Microsoft SQL Server 2000 Standard Edition
- Microsoft SQL Server 2000 64-bit Edition
- Microsoft SQL Server 7.0 Standard Edition
- Microsoft SQL Server 6.5 Standard Edition
- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2005 Express Edition
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Workgroup Edition
- Microsoft SQL Server 2008 Standard
- Microsoft SQL Server 2008 Analysis Services
- Microsoft SQL Server 2008 Developer
- Microsoft SQL Server 2008 Enterprise
- Microsoft SQL Server 2008 Enterprise Evaluation
- Microsoft SQL Server 2008 Express
- Microsoft SQL Server 2008 Express with Advanced Services
- Microsoft SQL Server 2008 Integration Services
- Microsoft SQL Server 2008 R2 Analysis Services
- Microsoft SQL Server 2008 R2 Datacenter
- Microsoft SQL Server 2008 R2 Developer
- Microsoft SQL Server 2008 R2 Enterprise
- Microsoft SQL Server 2008 R2 Express
- Microsoft SQL Server 2008 R2 Express with Advanced Services
- Microsoft SQL Server 2008 R2 Reporting Services
- Microsoft SQL Server 2008 R2 Standard
- Microsoft SQL Server 2008 R2 Standard Edition for Small Business
- Microsoft SQL Server 2008 R2 Web
- Microsoft SQL Server 2008 R2 Workgroup
- Microsoft SQL Server 2008 Reporting Services
- Microsoft SQL Server 2008 Standard Edition for Small Business
- Microsoft SQL Server 2008 Web
- Microsoft SQL Server 2008 Workgroup
- Microsoft SQL Server 2012 Developer
- Microsoft SQL Server 2012 Enterprise
- Microsoft SQL Server 2012 Express
- Microsoft SQL Server 2012 Standard
- Microsoft SQL Server 2012 Web
- Microsoft SQL Server 2012 Business Intelligence
- Microsoft SQL Server 2012 Enterprise Core
- Microsoft SQL Server 2014 Business Intelligence
- Microsoft SQL Server 2014 Developer
- Microsoft SQL Server 2014 Enterprise
- Microsoft SQL Server 2014 Enterprise Core
- Microsoft SQL Server 2014 Express
- Microsoft SQL Server 2014 Standard
- Microsoft SQL Server 2014 Web
Reference:
https://support.microsoft.com/en-us/kb/321185