Understanding the different versions and builds of Microsoft SQL Server is crucial for database administrators, IT professionals, and developers alike. Knowing your SQL Server version is essential for compatibility, security patching, and leveraging the latest features. This comprehensive Sql Server Versions Chart provides an in-depth look at the various releases, from the latest SQL Server 2025 to legacy editions, helping you identify your current version and explore the history of this powerful database management system.
This guide goes beyond a simple list, offering a detailed breakdown of each SQL Server version, including its release year, internal version number, and links to official Microsoft resources for further information. Whether you’re planning an upgrade, troubleshooting compatibility issues, or simply curious about the evolution of SQL Server, this chart is your go-to resource for navigating the landscape of SQL Server versions.
| Version | Release | Year |
|---|---|---|
| 17.0 | SQL Server 2025 | Announced |
| 16.0 | SQL Server 2022 | 2022 |
| 15.0 | SQL Server 2019 | 2019 |
| 14.0 | SQL Server 2017 | 2017 |
| 13.0 | SQL Server 2016 | 2016 |
| 12.0 | SQL Server 2014 | 2014 |
| 11.0 | SQL Server 2012 | 2012 |
| 10.50 | SQL Server 2008 R2 | 2010 |
| 10.0 | SQL Server 2008 | 2008 |
| 9.0 | SQL Server 2005 | 2005 |
| 8.0 | SQL Server 2000 | 2000 |
| 7.0 | SQL Server 7.0 | 1998 |
| 6.5 | SQL Server 6.5 | 1996 |
| 6.0 | SQL Server 6.0 | 1995 |
Identifying Your SQL Server Version
Before diving into the detailed chart, you might need a quick way to identify the SQL Server version you are currently running. Here are a few common methods:
-
Using SQL Server Management Studio (SSMS): Connect to your SQL Server instance using SSMS. Right-click on the server instance in Object Explorer, and select “Properties”. In the Server Properties window, look for the “Version” field. This will display the full version information, including the build number.
-
Using Transact-SQL (T-SQL): Open a new query window in SSMS or any SQL client and execute the following query:
SELECT @@VERSIONThis query will return a string containing detailed version information about your SQL Server instance.
-
Using SQL Server Configuration Manager: Open SQL Server Configuration Manager. In the left pane, select “SQL Server Services”. In the right pane, locate your SQL Server instance. The “Version” column may display the version, or you can right-click the service, select “Properties”, and find the version information on the “Service” tab.
These methods will help you determine your SQL Server version and then use the chart below for more detailed information.
Quick Summary of SQL Server Versions and Latest Updates
This section provides a summarized overview of recent and actively supported SQL Server versions, including their Release To Manufacturing (RTM) versions and the latest Cumulative Updates (CUs) or Service Packs (SPs).
| Release | RTM (Gold, no SP) | Latest Update |
|---|---|---|
| SQL Server 2025 (SQL Server 17.0) | Announced – Preview Available | – |
| SQL Server 2022 (SQL Server 16.0) | 16.0.1000.6 | Cumulative Update 17 (CU17) (16.0.4175.1, January 2025) |
| SQL Server 2019 (SQL Server 15.0) | 15.0.2000.5 | Cumulative Update 32 (CU32) (15.0.4430.1, February 2025) |
| SQL Server 2017 (SQL Server 14.0) | 14.0.1000.169 | Cumulative Update 31 (CU31) (14.0.3456.2, September 2022) |
| SQL Server 2016 (SQL Server 13.0) | 13.0.1601.5 | Service Pack 3 (SP3) + Cumulative Update 17 (CU17) for SP2 (13.0.5888.11, March 2021) |
Note: Starting with SQL Server 2017, Service Packs are no longer released. Microsoft provides Cumulative Updates (CUs) as the primary method for delivering fixes and improvements.
Microsoft SQL Server 2022 Builds
SQL Server 2022 is the latest generally available version, offering significant enhancements in performance, security, and cloud integration. Codenamed “Dallas”, it builds upon previous versions to provide a modern data platform.
| Build | Alternative builds | File version | Q | KB | KB / Description | Release Date |
|---|---|---|---|---|---|---|
| 16.0.4175.1 | 16.00.4175.1 | 2022.160.4175.1 | 5048038 | Cumulative update 17 (CU17) for SQL Server 2022 Latest CU | January 2025 | |
| 16.0.4165.4 | 16.00.4165.4 | 2022.160.4165.4 | 5048033 | Cumulative update 16 (CU16) for SQL Server 2022 | December 2024 | |
| 16.0.4155.4 | 16.00.4155.4 | 2022.160.4155.4 | Q5046862 | KB5046862 | Security update for SQL Server 2022 CU15: November 12, 2024 CVE-2024-49021 CVE-2024-49043 | November 2024 |
| 16.0.4150.1 | 16.00.4150.1 | 2022.160.4150.1 | Q5046059 | KB5046059 | Security update for SQL Server 2022 CU15: October 8, 2024 CVE-2024-37341 | October 2024 |
| 16.0.4145.4 | 16.00.4145.4 | 2022.160.4145.4 | 5041321 | Cumulative update 15 (CU15) for SQL Server 2022 | September 2024 | |
| … | … | … | … | … | … | … |
| 16.0.1000.6 | 16.00.1000.6 | 2022.160.1000.6 | Microsoft SQL Server 2022 RTM RTM | 2022 |
Microsoft SQL Server 2019 Builds
SQL Server 2019, codenamed “Aris Seattle”, introduced Big Data Clusters and enhanced features for intelligent database capabilities and improved performance.
| Build | Alternative builds | File version | Q | KB | KB / Description | Release Date |
|---|---|---|---|---|---|---|
| 15.0.4430.1 | 15.00.4430.1 | 2019.150.4430.1 | 5054833 | Cumulative update 32 (CU32) for SQL Server 2019 Latest CU | February 2025 | |
| 15.0.4420.2 | 15.00.4420.2 | 2019.150.4420.2 | 5049296 | Cumulative update 31 (CU31) for SQL Server 2019 | December 2024 | |
| 15.0.4415.2 | 15.00.4415.2 | 2019.150.4415.2 | 5049235 | Cumulative update 30 (CU30) for SQL Server 2019 | December 2024 | |
| 15.0.4410.1 | 15.00.4410.1 | 2019.150.4410.1 | Q5046860 | KB5046860 | Security update for SQL Server 2019 CU29: November 12, 2024 CVE-2024-38255 CVE-2024-43459 CVE-2024-43462 CVE-2024-48993 CVE-2024-48994 CVE-2024-48995 CVE-2024-48996 CVE-2024-48997 CVE-2024-48998 CVE-2024-48999 CVE-2024-49000 CVE-2024-49001 CVE-2024-49002 CVE-2024-49003 CVE-2024-49004 CVE-2024-49005 CVE-2024-49006 CVE-2024-49007 CVE-2024-49008 CVE-2024-49009 CVE-2024-49010 CVE-2024-49011 CVE-2024-49012 CVE-2024-49013 CVE-2024-49014 CVE-2024-49015 CVE-2024-49016 CVE-2024-49017 CVE-2024-49018 CVE-2024-49021 CVE-2024-49043 | November 2024 |
| 15.0.4405.4 | 15.00.4405.4 | 2019.150.4405.4 | 5046365 | Cumulative update 29 (CU29) for SQL Server 2019 | November 2024 | |
| … | … | … | … | … | … | … |
| 15.0.2000.5 | 15.00.2000.5 | 2019.150.2000.5 | Microsoft SQL Server 2019 RTM RTM | 2019 |
Microsoft SQL Server 2017 Builds
SQL Server 2017, known as “vNext” during development, brought SQL Server to Linux, alongside significant enhancements to in-database machine learning and adaptive query processing.
| Build | Alternative builds | File version | Q | KB | KB / Description | Release Date |
|---|---|---|---|---|---|---|
| 14.0.3485.1 | 14.00.3485.1 | 2017.140.3485.1 | Q5046858 | KB5046858 | Security update for SQL Server 2017 CU31: November 12, 2024 CVE-2024-38255 CVE-2024-43459 CVE-2024-43462 CVE-2024-48993 CVE-2024-48994 CVE-2024-48995 CVE-2024-48996 CVE-2024-48997 CVE-2024-48998 CVE-2024-48999 CVE-2024-49000 CVE-2024-49001 CVE-2024-49002 CVE-2024-49003 CVE-2024-49004 CVE-2024-49005 CVE-2024-49006 CVE-2024-49007 CVE-2024-49008 CVE-2024-49009 CVE-2024-49010 CVE-2024-49011 CVE-2024-49012 CVE-2024-49013 CVE-2024-49014 CVE-2024-49015 CVE-2024-49016 CVE-2024-49017 CVE-2024-49018 CVE-2024-49021 CVE-2024-49043 | November 2024 |
| 14.0.3480.1 | 14.00.3480.1 | 2017.140.3480.1 | Q5046061 | KB5046061 | Security update for SQL Server 2017 CU31: October 8, 2024 CVE-2024-37341 | October 2024 |
| 14.0.3475.1 | 14.00.3475.1 | 2017.140.3475.1 | Q5042215 | KB5042215 | Security update for SQL Server 2017 CU31: September 10, 2024 CVE-2024-26186 CVE-2024-26191 CVE-2024-37335 CVE-2024-37337 CVE-2024-37338 CVE-2024-37339 CVE-2024-37340 CVE-2024-37341 CVE-2024-37342 CVE-2024-37965 CVE-2024-37966 CVE-2024-37980 CVE-2024-43474 | September 2024 |
| 14.0.3471.2 | 14.00.3471.2 | 2017.140.3471.2 | Q5040940 | KB5040940 | Security update for SQL Server 2017 CU31: July 9, 2024 CVE-2024-20701 CVE-2024-21303 CVE-2024-21308 CVE-2024-21317 CVE-2024-21331 CVE-2024-21332 CVE-2024-21333 CVE-2024-21335 CVE-2024-21373 CVE-2024-21398 CVE-2024-21414 CVE-2024-21415 CVE-2024-21425 CVE-2024-21428 CVE-2024-21449 CVE-2024-35271 CVE-2024-35272 CVE-2024-37318 CVE-2024-37319 CVE-2024-37320 CVE-2024-37321 CVE-2024-37322 CVE-2024-37323 CVE-2024-37324 CVE-2024-37326 CVE-2024-37327 CVE-2024-37328 CVE-2024-37329 CVE-2024-37330 CVE-2024-37331 CVE-2024-37332 CVE-2024-37333 CVE-2024-37336 CVE-2024-38087 CVE-2024-38088 | July 2024 |
| 14.0.3465.1 | 14.00.3465.1 | 2017.140.3465.1 | Q5029376 | KB5029376 | Security update for SQL Server 2017 CU31: October 10, 2023 CVE-2023-36728 | October 2023 |
| 14.0.3460.9 | 14.00.3460.9 | 2017.140.3460.9 | Q5021126 | KB5021126 | Security update for SQL Server 2017 CU31: February 14, 2023 CVE-2023-21528 CVE-2023-21704 CVE-2023-21705 CVE-2023-21713 CVE-2023-21718 | February 2023 |
| 14.0.3456.2 | 14.00.3456.2 | 2017.140.3456.2 | 5016884 | Cumulative update 31 (CU31) for SQL Server 2017 Latest CU | September 2022 | |
| … | … | … | … | … | … | … |
| 14.0.1000.169 | 14.00.1000.169 | 2017.140.1000.169 | Microsoft SQL Server 2017 RTM RTM | 2017 |
Microsoft SQL Server 2016 Builds
SQL Server 2016, released with codename “SQL Server 13” or “SQL Server vNext”, focused on enhancing performance, security, and business intelligence capabilities. This was the last version to receive Service Packs.
| Build | Alternative builds | File version | SP | CU | KB | KB / Description | Release Date |
|---|---|---|---|---|---|---|---|
| 13.0.7050.2 | 13.00.7050.2 | 2015.131.7050.2 | SP3 | KB5046856 | Security update for SQL Server 2016 SP3 Azure Connect Feature Pack: November 12, 2024 CVE-2024-38255 CVE-2024-43459 CVE-2024-43462 CVE-2024-48993 CVE-2024-48994 CVE-2024-48995 CVE-2024-48996 CVE-2024-48997 CVE-2024-48998 CVE-2024-48999 CVE-2024-49000 CVE-2024-49001 CVE-2024-49002 CVE-2024-49003 CVE-2024-49004 CVE-2024-49005 CVE-2024-49006 CVE-2024-49007 CVE-2024-49008 CVE-2024-49009 CVE-2024-49010 CVE-2024-49011 CVE-2024-49012 CVE-2024-49013 CVE-2024-49014 CVE-2024-49015 CVE-2024-49016 CVE-2024-49017 CVE-2024-49018 CVE-2024-49021 CVE-2024-49043 | November 2024 | |
| 13.0.7045.2 | 13.00.7045.2 | 2015.131.7045.2 | SP3 | KB5046062 | Security update for SQL Server 2016 SP3 Azure Connect Feature Pack: October 8, 2024 CVE-2024-37341 | October 2024 | |
| 13.0.7040.1 | 13.00.7040.1 | 2015.131.7040.1 | SP3 | KB5042209 | Security update for SQL Server 2016 SP3 Azure Connect Feature Pack: September 10, 2024 CVE-2024-37341 CVE-2024-37965 CVE-2024-37980 | September 2024 | |
| 13.0.7037.1 | 13.00.7037.1 | 2015.131.7037.1 | SP3 | KB5040944 | Security update for SQL Server 2016 SP3 Azure Connect Feature Pack: July 9, 2024 CVE-2024-20701 CVE-2024-21303 CVE-2024-21308 CVE-2024-21317 CVE-2024-21331 CVE-2024-21332 CVE-2024-21333 CVE-2024-21335 CVE-2024-21373 CVE-2024-21398 CVE-2024-21414 CVE-2024-21415 CVE-2024-21425 CVE-2024-21428 CVE-2024-21449 CVE-2024-35271 CVE-2024-35272 CVE-2024-37318 CVE-2024-37319 CVE-2024-37320 CVE-2024-37321 CVE-2024-37322 CVE-2024-37323 CVE-2024-37324 CVE-2024-37326 CVE-2024-37327 CVE-2024-37328 CVE-2024-37329 CVE-2024-37330 CVE-2024-37331 CVE-2024-37332 CVE-2024-37333 CVE-2024-37336 CVE-2024-38087 CVE-2024-38088 | July 2024 | |
| 13.0.7029.3 | 13.00.7029.3 | 2015.131.7029.3 | SP3 | KB5029187 | Security update for SQL Server 2016 SP3 Azure Connect Feature Pack: October 10, 2023 CVE-2023-36728 | October 2023 | |
| 13.0.7024.30 | 13.00.7024.30 | 2015.131.7024.30 | SP3 | KB5021128 | Security update for SQL Server 2016 SP3 Azure Connect Feature Pack: February 14, 2023 CVE-2023-21528 CVE-2023-21704 CVE-2023-21705 CVE-2023-21713 CVE-2023-21718 | February 2023 | |
| 13.0.7016.1 | 13.00.7016.1 | 2015.131.7016.1 | SP3 | KB5015371 | Security update for SQL Server 2016 SP3 Azure Connect Feature Pack: June 14, 2022 CVE-2022-29143 | June 2022 | |
| 13.0.7000.253 | 13.00.7000.253 | 2015.131.7000.253 | SP3 | KB5014242 | Azure Connect Feature Pack for SQL Server 2016 Service Pack 3 | May 2022 | |
| 13.0.6455.2 | 13.00.6455.2 | 2015.131.6455.2 | SP3 | KB5046855 | Security update for SQL Server 2016 SP3 GDR: November 12, 2024 CVE-2024-38255 CVE-2024-43459 CVE-2024-43462 CVE-2024-48993 CVE-2024-48994 CVE-2024-48995 CVE-2024-48996 CVE-2024-48997 CVE-2024-48998 CVE-2024-48999 CVE-2024-49000 CVE-2024-49001 CVE-2024-49002 CVE-2024-49003 CVE-2024-49004 CVE-2024-49005 CVE-2024-49006 CVE-2024-49007 CVE-2024-49008 CVE-2024-49009 CVE-2024-49010 CVE-2024-49011 CVE-2024-49012 CVE-2024-49013 CVE-2024-49014 CVE-2024-49015 CVE-2024-49016 CVE-2024-49017 CVE-2024-49018 CVE-2024-49021 CVE-2024-49043 | November 2024 | |
| 13.0.6450.1 | 13.00.6450.1 | 2015.131.6450.1 | SP3 | KB5046063 | Security update for SQL Server 2016 SP3 GDR: October 8, 2024 CVE-2024-37341 | October 2024 | |
| 13.0.6445.1 | 13.00.6445.1 | 2015.131.6445.1 | SP3 | KB5042207 | Security update for SQL Server 2016 SP3 GDR: September 10, 2024 CVE-2024-37341 CVE-2024-37965 CVE-2024-37980 | September 2024 | |
| 13.0.6441.1 | 13.00.6441.1 | 2015.131.6441.1 | SP3 | KB5040946 | Security update for SQL Server 2016 SP3 GDR: July 9, 2024 CVE-2024-20701 CVE-2024-21303 CVE-2024-21308 CVE-2024-21317 CVE-2024-21331 CVE-2024-21332 CVE-2024-21333 CVE-2024-21335 CVE-2024-21373 CVE-2024-21398 CVE-2024-21414 CVE-2024-21415 CVE-2024-21425 CVE-2024-21428 CVE-2024-21449 CVE-2024-35271 CVE-2024-35272 CVE-2024-37318 CVE-2024-37319 CVE-2024-37320 CVE-2024-37321 CVE-2024-37322 CVE-2024-37323 CVE-2024-37324 CVE-2024-37326 CVE-2024-37327 CVE-2024-37328 CVE-2024-37329 CVE-2024-37330 CVE-2024-37331 CVE-2024-37332 CVE-2024-37333 CVE-2024-37336 CVE-2024-38087 CVE-2024-38088 | July 2024 | |
| 13.0.6435.1 | 13.00.6435.1 | 2015.131.6435.1 | SP3 | KB5029186 | Security update for SQL Server 2016 SP3 GDR: October 10, 2023 CVE-2023-36728 | October 2023 | |
| 13.0.6430.49 | 13.00.6430.49 | 2015.131.6430.49 | SP3 | KB5021129 | Security update for SQL Server 2016 SP3 GDR: February 14, 2023 CVE-2023-21528 CVE-2023-21704 CVE-2023-21705 CVE-2023-21713 CVE-2023-21718 | February 2023 | |
| 13.0.6419.1 | 13.00.6419.1 | 2015.131.6419.1 | SP3 | KB5014355 | Security update for SQL Server 2016 SP3 GDR: June 14, 2022 CVE-2022-29143 | June 2022 | |
| 13.0.6404.1 | 13.00.6404.1 | 2015.131.6404.1 | SP3 | KB5006943 | On-demand hotfix update package for SQL Server 2016 Service Pack 3 (SP3) | November 2021 | |
| 13.0.6300.2 | 13.00.6300.2 | 2015.131.6300.2 | SP3 | KB5003279 | Microsoft SQL Server 2016 Service Pack 3 (SP3) Latest SP CVE-2015-6420 CVE-2017-15708 | May 2021 | |
| … | … | … | … | … | … | … | |
| 13.0.5893.48 | 13.00.5893.48 | 2015.131.5893.48 | SP2 | CU17 | KB5014351 | Security update for SQL Server 2016 SP2 CU17: June 14, 2022 CVE-2022-29143 | June 2022 |
| 13.0.5888.11 | 13.00.5888.11 | 2015.131.5888.11 | SP2 | CU17 | KB5001092 | Cumulative update 17 (CU17) for SQL Server 2016 Service Pack 2 Latest CU | March 2021 |
| 13.0.5882.1 | 13.00.5882.1 | 2015.131.5882.1 | SP2 | CU16 | KB5000645 | Cumulative update 16 (CU16) for SQL Server 2016 Service Pack 2 | January 2021 |
| 13.0.5865.1 | 13.00.5865.1 | 2015.131.5865.1 | SP2 | CU15 | KB4583461 | Security update for SQL Server 2016 SP2 CU15: January 12, 2021 CVE-2021-1636 | January 2021 |
| … | … | … | … | … | … | … | |
| 13.0.1601.5 | 13.00.1601.5 | 2015.130.1601.5 | RTM | Microsoft SQL Server 2016 RTM RTM | 2016 |
Obsolete SQL Server Versions (Out of Support)
The following versions of SQL Server are no longer supported by Microsoft. While they are listed for historical purposes and to help identify older systems, it is highly recommended to upgrade to a supported version for security and feature updates.
Microsoft SQL Server 2014 Builds
SQL Server 2014, with the codename “Hekaton”, introduced in-memory OLTP capabilities and further enhanced cloud integration and scalability.
| Build | Alternative builds | File version | SP | CU | KB | KB / Description | Release Date |
|---|---|---|---|---|---|---|---|
| 12.0.6449.1 | 12.00.6449.1 | 2014.120.6449.1 | SP3 | CU4 | KB5029185 | Security update for SQL Server 2014 SP3 CU4: October 10, 2023 CVE-2023-36728 | October 2023 |
| 12.0.6444.4 | 12.00.6444.4 | 2014.120.6444.4 | SP3 | CU4 | KB5021045 | Security update for SQL Server 2014 SP3 CU4: February 14, 2023 CVE-2023-21528 CVE-2023-21704 CVE-2023-21705 CVE-2023-21713 CVE-2023-21718 | February 2023 |
| 12.0.6439.10 | 12.00.6439.10 | 2014.120.6439.10 | SP3 | CU4 | KB5014164 | Security update for SQL Server 2014 SP3 CU4: June 14, 2022 CVE-2022-29143 | June 2022 |
| 12.0.6433.1 | 12.00.6433.1 | 2014.120.6433.1 | SP3 | CU4 | KB4583462 | Security update for SQL Server 2014 SP3 CU4: January 12, 2021 CVE-2021-1636 | January 2021 |
| 12.0.6372.1 | 12.00.6372.1 | 2014.120.6372.1 | SP3 | CU4 | KB4535288 | Security update for SQL Server 2014 SP3 CU4: February 11, 2020 CVE-2020-0618 | February 2020 |
| 12.0.6329.1 | 12.00.6329.1 | 2014.120.6329.1 | SP3 | CU4 | KB4500181 | Cumulative update package 4 (CU4) for SQL Server 2014 Service Pack 3 Latest CU | July 2019 |
| … | … | … | … | … | … | … | |
| 12.0.6293.0 | 12.00.6293.0 | 2014.120.6293.0 | SP3 | GDR | KB4505422 | Security update for SQL Server 2014 SP3 CU3 GDR: July 9, 2019 CVE-2019-1068 | July 2019 |
| 12.0.6259.0 | 12.00.6259.0 | 2014.120.6259.0 | SP3 | CU3 | KB4491539 | Cumulative update package 3 (CU3) for SQL Server 2014 Service Pack 3 | April 2019 |
| 12.0.6214.1 | 12.00.6214.1 | 2014.120.6214.1 | SP3 | CU2 | KB4482960 | Cumulative update package 2 (CU2) for SQL Server 2014 Service Pack 3 | February 2019 |
| 12.0.6205.1 | 12.00.6205.1 | 2014.120.6205.1 | SP3 | CU1 | KB4470220 | Cumulative update package 1 (CU1) for SQL Server 2014 Service Pack 3 | December 2018 |
| 12.0.6024.0 | 12.00.6024.0 | 2014.120.6024.0 | SP3 | KB4022619 | SQL Server 2014 Service Pack 3 (SP3) Latest SP | June 2018 | |
| … | … | … | … | … | … | … | |
| 12.0.5687.1 | 12.00.5687.1 | 2014.120.5687.1 | SP2 | CU18 | KB4500180 | Cumulative update package 18 (CU18) for SQL Server 2014 Service Pack 2 | June 2019 |
| 12.0.5659.1 | 12.00.5659.1 | 2014.120.5659.1 | SP2 | GDR | KB4505419 | Security update for SQL Server 2014 SP2 CU17 GDR: July 9, 2019 CVE-2019-1068 | July 2019 |
| 12.0.5632.1 | 12.00.5632.1 | 2014.120.5632.1 | SP2 | CU17 | KB4491540 | Cumulative update package 17 (CU17) for SQL Server 2014 Service Pack 2 | April 2019 |
| 12.0.5626.1 | 12.00.5626.1 | 2014.120.5626.1 | SP2 | CU16 | KB4482967 | Cumulative update package 16 (CU16) for SQL Server 2014 Service Pack 2 | February 2019 |
| … | … | … | … | … | … | … | |
| 12.0.2000.8 | 12.00.2000.8 | 2014.120.2000.8 | RTM | SQL Server 2014 RTM RTM | 2014 |
Microsoft SQL Server 2012 Builds
SQL Server 2012, codenamed “Denali”, focused on high availability, cloud readiness, and new features like AlwaysOn Availability Groups and ColumnStore indexes.
| Build | Alternative builds | File version | SP | CU | KB | KB / Description | Release Date |
|---|---|---|---|---|---|---|---|
| 11.0.7512.11 | 11.00.7512.11 | 2011.110.7512.11 | SP4 | GDR | KB5021123 | Security update for SQL Server 2012 SP4 GDR: February 14, 2023 CVE-2023-21528 CVE-2023-21705 CVE-2023-21713 | February 2023 |
| 11.0.7507.2 | 11.00.7507.2 | 2011.110.7507.2 | SP4 | GDR | KB4583465 | Security update for SQL Server 2012 SP4 GDR: January 12, 2021 CVE-2021-1636 | January 2021 |
| 11.0.7493.4 | 11.00.7493.4 | 2011.110.7493.4 | SP4 | GDR | KB4532098 | Security update for SQL Server 2012 SP4 GDR: February 11, 2020 CVE-2020-0618 | February 2020 |
| 11.0.7469.6 | 11.00.7469.6 | 2011.110.7469.6 | SP4 | KB4091266 | On-demand hotfix update package for SQL Server 2012 SP4 | April 2018 | |
| 11.0.7462.6 | 11.00.7462.6 | 2011.110.7462.6 | SP4 | GDR | KB4057116 | Security update for SQL Server 2012 SP4 GDR: January 12, 2018 – Security Advisory ADV180002 CVE-2017-5715 CVE-2017-5753 CVE-2017-5754 | January 2018 |
| 11.0.7001.0 | 11.00.7001.0 | 2011.110.7001.0 | SP4 | KB4057121 | SQL Server 2012 Service Pack 4 (SP4) Latest SP | June 2017 | |
| … | … | … | … | … | … | … | |
| 11.0.6615.2 | 11.00.6615.2 | 2012.110.6615.2 | SP3 | CU10 | KB4057121 | Security update for SQL Server 2012 SP3 CU: January 16, 2018 – Security Advisory ADV180002 CVE-2017-5715 CVE-2017-5753 CVE-2017-5754 | January 2018 |
| 11.0.6607.3 | 11.00.6607.3 | 2011.110.6607.3 | SP3 | CU10 | KB4025925 | Cumulative update package 10 (CU10) for SQL Server 2012 Service Pack 3 Latest CU CVE-2017-8516 | October 2017 |
| 11.0.6607.3 | 11.00.6607.3 | 2011.110.6607.3 | SP3 | CU10 | KB4019090 | Security update for SQL Server 2012 Service Pack 3 CU: August 8, 2017 CVE-2017-8516 | August 2017 |
| … | … | … | … | … | … | … | |
| 11.0.6020.0 | 11.00.6020.0 | 2011.110.6020.0 | SP3 | KB49996 | SQL Server 2012 Service Pack 3 (SP3) | June 2015 | |
| … | … | … | … | … | … | … | |
| 11.0.2100.60 | 11.00.2100.60 | 2011.110.2100.60 | RTM | SQL Server 2012 RTM RTM | 2012 |
Microsoft SQL Server 2008 R2 Builds
SQL Server 2008 R2, codenamed “Kilimanjaro”, enhanced enterprise scalability, BI capabilities with PowerPivot and StreamInsight, and mission-critical performance.
| Build | Alternative builds | File version | SP | CU | KB | KB / Description | Release Date |
|---|---|---|---|---|---|---|---|
| 10.50.6785.2 | 2009.100.6785.2 | 2009.100.6785.2 | SP3 | GDR | KB5021112 | Security update for SQL Server 2008 R2 SP3 GDR: February 14, 2023 CVE-2023-21528 | February 2023 |
| 10.50.6560.0 | 2009.100.6560.0 | 2009.100.6560.0 | SP3 | GDR | KB4057113 | Security update for SQL Server 2008 R2 SP3 GDR: January 6, 2018 – Security Advisory ADV180002 CVE-2017-5715 CVE-2017-5753 CVE-2017-5754 | January 2018 |
| 10.50.6549.0 | 2009.100.6549.0 | 2009.100.6549.0 | SP3 | KB3146034 | Intermittent service terminations occur after you install any SQL Server 2008 or SQL Server 2008 R2 versions from KB3135244 | May 2016 | |
| 10.50.6537.0 | 2009.100.6537.0 | 2009.100.6537.0 | SP3 | KB3135244 | TLS 1.2 support for SQL Server 2008 R2 SP3 | January 2016 | |
| 10.50.6529.0 | 2009.100.6529.0 | 2009.100.6529.0 | SP3 | QFE | KB3045314 | MS15-058: Description of the security update for SQL Server 2008 R2 Service Pack 3 QFE: July 14, 2015 | July 2015 |
| 10.50.6525.0 | 2009.100.6525.0 | 2009.100.6525.0 | SP3 | KB3033860 | An on-demand hotfix update package is available for SQL Server 2008 R2 Service Pack 3 (SP3) | March 2015 | |
| 10.50.6220.0 | 2009.100.6220.0 | 2009.100.6220.0 | SP3 | GDR | KB3045316 | MS15-058: Description of the security update for SQL Server 2008 R2 Service Pack 3 GDR: July 14, 2015 | July 2015 |
| 10.50.6000.34 | 2009.100.6000.34 | 2009.100.6000.34 | SP3 | KB44271 | SQL Server 2008 R2 Service Pack 3 (SP3) Latest SP | July 2014 | |
| … | … | … | … | … | … | … | |
| 10.50.1600.1 | 2009.100.1600.1 | 2009.100.1600.1 | RTM | SQL Server 2008 R2 RTM RTM | 2010 |
Microsoft SQL Server 2008 Builds
SQL Server 2008, codenamed “Katmai” or “Akaida”, emphasized manageability, developer productivity, and data platform enhancements.
| Build | Alternative builds | File version | SP | CU | KB | KB / Description | Release Date |
|---|---|---|---|---|---|---|---|
| 10.0.6814.4 | 10.00.6814.4 | 2007.100.6814.4 | SP4 | GDR | KB5020863 | Security update for SQL Server 2008 SP4 GDR: February 14, 2023 CVE-2023-21528 | February 2023 |
| 10.0.6556.0 | 10.00.6556.0 | 2007.100.6556.0 | SP4 | GDR | KB4057114 | Security update for SQL Server 2008 SP4 GDR: January 6, 2018 – Security Advisory ADV180002 CVE-2017-5715 CVE-2017-5753 CVE-2017-5754 | January 2018 |
| 10.0.6547.0 | 10.00.6547.0 | 2007.100.6547.0 | SP4 | KB3146034 | Intermittent service terminations occur after you install any SQL Server 2008 or SQL Server 2008 R2 versions from KB3135244 | May 2016 | |
| 10.0.6543.0 | 10.00.6543.0 | 2007.100.6543.0 | SP4 | KB3135244 | TLS 1.2 support for SQL Server 2008 SP4 | January 2016 | |
| 10.0.6535.0 | 10.00.6535.0 | 2007.100.6535.0 | SP4 | QFE | KB3045308 | MS15-058: Description of the security update for SQL Server 2008 Service Pack 4 QFE: July 14, 2015 | July 2015 |
| 10.0.6526.0 | 10.00.6526.0 | 2007.100.6526.0 | SP4 | KB3034373 | An on-demand hotfix update package is available for SQL Server 2008 Service Pack 4 (SP4) | March 2015 | |
| 10.0.6241.0 | 10.00.6241.0 | 2007.100.6241.0 | SP4 | GDR | KB3045311 | MS15-058: Description of the security update for SQL Server 2008 Service Pack 4 GDR: July 14, 2015 | July 2015 |
| 10.0.6000.29 | 10.00.6000.29 | 2007.100.6000.29 | SP4 | KB44278 | SQL Server 2008 Service Pack 4 (SP4) Latest SP | April 2014 | |
| … | … | … | … | … | … | … | |
| 10.0.1600.22 | 10.00.1600.22 | 2007.100.1600.22 | RTM | SQL Server 2008 RTM RTM | 2008 |
Microsoft SQL Server 2005 Builds
SQL Server 2005, known during development as “Yukon”, was a major release focusing on enhancing developer productivity, reliability, and availability.
| Build | Alternative builds | File version | SP | CU | KB | KB / Description | Release Date |
|---|---|---|---|---|---|---|---|
| 9.0.5324 | 9.00.5324 | 2005.90.5324.0 | SP4 | QFE | KB2716427 | MS12-070: Description of the security update for SQL Server 2005 Service Pack 4 QFE | October 2012 |
| 9.0.5296 | 9.00.5296 | 2005.90.5296.0 | SP4 | KB2615425 | FIX: “Msg 7359” error when a view uses another view in SQL Server 2005 if the schema version of a remote table is updated | February 2012 | |
| 9.0.5295 | 9.00.5295 | 2005.90.5295.0 | SP4 | KB2598903 | FIX: SQL Server Agent job randomly stops when you schedule the job to run past midnight on specific days in SQL Server 2005, in SQL Server 2008 or in SQL Server 2008 R2 | October 2011 | |
| 9.0.5294 | 9.00.5294 | 2005.90.5294.0 | SP4 | KB2572407 | FIX: Error 5180 when you use the ONLINE option to rebuild an index in SQL Server 2005 | August 2011 | |
| 9.0.5292 | 9.00.5292 | 2005.90.5292.0 | SP4 | QFE | KB2494123 | MS11-049: Description of the security update for SQL Server 2005 Service Pack 4 QFE: June 14, 2011 | June 2011 |
| 9.0.5266 | 9.00.5266 | 2005.90.5266.0 | SP4 | CU3 | KB2507769 | Cumulative update package 3 (CU3) for SQL Server 2005 Service Pack 4 | July 2011 |
| 9.0.5259 | 9.00.5259 | 2005.90.5259.0 | SP4 | CU2 | KB2489409 | Cumulative update package 2 (CU2) for SQL Server 2005 Service Pack 4 | June 2011 |
| 9.0.5254 | 9.00.5254 | 2005.90.5254.0 | SP4 | CU1 | KB2464079 | Cumulative update package 1 (CU1) for SQL Server 2005 Service Pack 4 | April 2011 |
| 9.0.5069 | 9.00.5069 | 2005.90.5069.0 | SP4 | KB2494120 | Microsoft Security Bulletin MS12-070 | October 2012 | |
| 9.0.5057 | 9.00.5057 | 2005.90.5057.0 | SP4 | GDR | KB2494120 | MS11-049: Description of the security update for SQL Server 2005 Service Pack 4 GDR: June 14, 2011 | June 2011 |
| 9.0.5000 | 9.00.5000 | 2005.90.5000.0 | SP4 | KB2463332 | SQL Server 2005 Service Pack 4 (SP4) Latest SP | December 2010 | |
| … | … | … | … | … | … | … | |
| 9.0.1399 | 9.00.1399 | 2005.90.1399.0 | RTM | SQL Server 2005 RTM RTM | 2005 |
Microsoft SQL Server 2000 Builds
SQL Server 2000, codenamed “Shiloh”, was a pivotal release, focusing on web integration, XML support, and scalability improvements. While obsolete, it remains relevant in understanding SQL Server’s evolution.
| Build | Alternative builds | File version | SP | CU | KB | KB / Description | Release Date |
|---|---|---|---|---|---|---|---|
| 8.0.2305 | 8.00.2305 | 2000.80.2305.0 | SP4 | QFE | KB983811 | MS12-060: Description of the security update for SQL Server 2000 Service Pack 4 QFE: August 14, 2012 | August 2012 |
| 8.0.2301 | 8.00.2301 | 2000.80.2301.0 | SP4 | QFE | KB983809 | MS12-027: Description of the security update for Microsoft SQL Server 2000 Service Pack 4 QFE: April 10, 2012 | April 2012 |
| 8.0.2283 | 8.00.2283 | 2000.80.2283.0 | SP4 | KB971524 | FIX: An access violation occurs when you run a DELETE statement or an UPDATE statement in the Itanium-based versions of SQL Server 2000 after you install security update MS09-004 | January 2010 | |
| 8.0.2282 | 8.00.2282 | 2000.80.2282.0 | SP4 | QFE | KB960083 | MS09-004: Description of the security update for SQL Server 2000 QFE and for MSDE 2000: February 10, 2009 | February 2009 |
| 8.0.2279 | 8.00.2279 | 2000.80.2279.0 | SP4 | KB959678 | FIX: When you run the SPSBackup.exe utility to back up a SQL Server 2000 database that is configured as a back-end database for a Windows SharePoint Services server, the backup operation fails | November 2008 | |
| 8.0.2273 | 8.00.2273 | 2000.80.2273.0 | SP4 | QFE | KB948111 | MS08-040: Description of the security update for SQL Server 2000 QFE and MSDE 2000 July 8, 2008 | July 2008 |
| 8.0.2271 | 8.00.2271 | 2000.80.2271.0 | SP4 | KB946584 | FIX: The SPACE function always returns one space in SQL Server 2000 if the SPACE function uses a collation that differs from the collation of the current database | June 2008 | |
| 8.0.2265 | 8.00.2265 | 2000.80.2265.0 | SP4 | KB944985 | FIX: The data on the publisher does not match the data on the subscriber when you synchronize a SQL Server 2005 Mobile Edition subscriber with a SQL Server 2000 “merge replication” publisher | April 2008 | |
| 8.0.2253 | 8.00.2253 | 2000.80.2253.0 | SP4 | KB939317 | FIX: The CPU utilization may suddenly increase to 100 percent when there are many connections to an instance of SQL Server 2000 on a computer that has multiple processors | October 2007 | |
| 8.0.2249 | 8.00.2249 | 2000.80.2249.0 | SP4 | KB936232 | FIX: An access violation may occur when you try to log in to an instance of SQL Server 2000 | September 2007 | |
| 8.0.2248 | 8.00.2248 | 2000.80.2248.0 | SP4 | KB935950 | FIX: The foreign key that you created between two tables does not work after you run the CREATE INDEX statement in SQL Server 2000 | August 2007 | |
| 8.0.2246 | 8.00.2246 | 2000.80.2246.0 | SP4 | KB935465 | An updated version of Sqlvdi.dll is now available for SQL Server 2000 | August 2007 | |
| 8.0.2245 | 8.00.2245 | 2000.80.2245.0 | SP4 | KB933573 | FIX: You may receive an assertion or database corruption may occur when you use the bcp utility or the “Bulk Insert” Transact-SQL command to import data in SQL Server 2000 | July 2007 | |
| 8.0.2244 | 8.00.2244 | 2000.80.2244.0 | SP4 | KB934203 | FIX: A hotfix for Microsoft SQL Server 2000 Service Pack 4 may not update all the necessary files on an x64-based computer | July 2007 | |
| 8.0.2242 | 8.00.2242 | 2000.80.2242.0 | SP4 | KB929131 | FIX: In SQL Server 2000, the synchronization process is slow, and the CPU usage is high on the computer that is configured as the Distributor | April 2007 | |
| 8.0.2238 | 8.00.2238 | 2000.80.2238.0 | SP4 | KB931932 | FIX: The merge agent fails intermittently when you use merge replication that uses a custom resolver after you install SQL Server 2000 Service Pack 4 | May 2007 | |
| 8.0.2236 | 8.00.2236 | 2000.80.2236.0 | SP4 | KB930484 | FIX: CPU utilization may approach 100 percent on a computer that is running SQL Server 2000 after you run the BACKUP DATABASE statement or the BACKUP LOG statement | April 2007 | |
| 8.0.2234 | 8.00.2234 | 2000.80.2234.0 | SP4 | KB929440 | FIX: Error messages when you try to update table rows or insert table rows into a table in SQL Server 2000: “644” or “2511” | April 2007 | |
| 8.0.2232 | 8.00.2232 | 2000.80.2232.0 | SP4 | KB928568 | FIX: SQL Server 2000 stops responding when you cancel a query or when a query time-out occurs, and error messages are logged in the SQL Server error log file | March 2007 | |
| 8.0.2231 | 8.00.2231 | 2000.80.2231.0 | SP4 | KB928079 | FIX: The Sqldumper.exe utility cannot generate a filtered SQL Server dump file when you use the Remote Desktop Connection service or Terminal Services to connect to a Windows 2000 Server-based computer in SQL Server 2000 | March 2007 | |
| 8.0.2229 | 8.00.2229 | 2000.80.2229.0 | SP4 | KB927186 | FIX: Error message when you create a merge replication for tables that have computed columns in SQL Server 2000 Service Pack 4: “The process could not log conflict information” | February 2007 | |
| 8.0.2226 | 8.00.2226 | 2000.80.2226.0 | SP4 | KB925684 | FIX: You may experience one or more symptoms when you run a “CREATE INDEX” statement on an instance of SQL Server 2000 | January 2007 | |
| 8.0.2226 | 8.00.2226 | 2000.80.2226.0 | SP4 | KB925732 | FIX: You may receive inconsistent comparison results when you compare strings by using a width sensitive collation in SQL Server 2000 | January 2007 | |
| 8.0.2223 | 8.00.2223 | 2000.80.2223.0 | SP4 | KB925419 | FIX: The server stops responding, the performance is slow, and a time-out occurs in SQL Server 2000 | January 2007 | |
| 8.0.2223 | 8.00.2223 | 2000.80.2223.0 | SP4 | KB925678 | FIX: Error message when you schedule a Replication Merge Agent job to run after you install SQL Server 2000 Service Pack 4: “The process could not enumerate changes at the ‘Subscriber'” | January 2007 | |
| 8.0.2218 | 8.00.2218 | 2000.80.2218.0 | SP4 | KB925297 | FIX: The result may be sorted in the wrong order when you run a query that uses the ORDER BY clause to sort a column in a table in SQL Server 2000 | December 2006 | |
| 8.0.2217 | 8.00.2217 | 2000.80.2217.0 | SP4 | KB924664 | FIX: You cannot stop the SQL Server service, or many minidump files and many log files are generated in SQL Server 2000 | December 2006 | |
| 8.0.2215 | 8.00.2215 | 2000.80.2215.0 | SP4 | KB923796 | FIX: Data in a subscriber of a merge publication in SQL Server 2000 differs from the data in the publisher | November 2006 | |
| 8.0.2215 | 8.00.2215 | 2000.80.2215.0 | SP4 | KB924662 | FIX: The query performance may be slow when you query data from a view in SQL Server 2000 | December 2006 | |
| 8.0.2215 | 8.00.2215 | 2000.80.2215.0 | SP4 | KB923563 | FIX: Error message when you configure an immediate updating transactional replication in SQL Server 2000: “Implicit conversion from datatype ‘text’ to ‘nvarchar’ is not allowed” | November 2006 | |
| 8.0.2215 | 8.00.2215 | 2000.80.2215.0 | SP4 | KB923327 | FIX: You may receive an access violation error message when you import data by using the “Bulk Insert” command in SQL Server 2000 | November 2006 | |
| 8.0.2209 | 8.00.2209 | 2000.80.2209.0 | SP4 | KB923797 | The Knowledge Base (KB) Article You Requested Is Currently Not Available | November 2006 | |
| 8.0.2207 | 8.00.2207 | 2000.80.2207.0 | SP4 | KB923344 | FIX: A SQL Server 2000 session may be blocked for the whole time that a Snapshot Agent job runs | November 2006 | |
| 8.0.2201 | 8.00.2201 | 2000.80.2201.0 | SP4 | KB920930 | FIX: Error message when you try to run a query on a linked server in SQL Server 2000 | October 2006 | |
| 8.0.2199 | 8.00.2199 | 2000.80.2199.0 | SP4 | KB919221 | FIX: SQL Server 2000 may take a long time to complete the synchronization phase when you create a merge publication | October 2006 | |
| 8.0.2197 | 8.00.2197 | 2000.80.2197.0 | SP4 | KB919133 | FIX: Each query takes a long time to compile when you execute a single query or when you execute multiple concurrent queries in SQL Server 2000 | October 2006 | |
| 8.0.2197 | 8.00.2197 | 2000.80.2197.0 | SP4 | KB919068 | FIX: The query may return incorrect results, and the execution plan for the query may contain a “Table Spool” operator in SQL Server 2000 | October 2006 | |
| 8.0.2197 | 8.00.2197 | 2000.80.2197.0 | SP4 | KB919399 | FIX: A profiler trace in SQL Server 2000 may stop logging events unexpectedly, and you may receive the following error message: “Failed to read trace data” | October 2006 | |
| 8.0.2196 | 8.00.2196 | 2000.80.2196.0 | SP4 | KB919165 | FIX: A memory leak occurs when you run a remote query by using a linked server in SQL Server 2000 | October 2006 | |
| 8.0.2194 | 8.00.2194 | 2000.80.2194.0 | SP4 | KB917565 | FIX: Error 17883 is logged in the SQL Server error log, and the instance of SQL Server 2000 temporarily stops responding | September 2006 | |
| 8.0.2194 | 8.00.2194 | 2000.80.2194.0 | SP4 | KB917972 | FIX: You receive an access violation error message when you try to perform a read of a large binary large object column in SQL Server 2000 | September 2006 | |
| 8.0.2192 | 8.00.2192 | 2000.80.2192.0 | SP4 | KB917606 | FIX: You may notice a decrease in performance when you run a query that uses the UNION ALL operator in SQL Server 2000 Service Pack 4 | September 2006 | |
| 8.0.2191 | 8.00.2191 | 2000.80.2191.0 | SP4 | KB916698 | FIX: Error message when you run SQL Server 2000: “Failed assertion = ‘lockFound == TRUE'” | August 2006 | |
| 8.0.2191 | 8.00.2191 | 2000.80.2191.0 | SP4 | KB916950 | FIX: You may experience heap corruption, and SQL Server 2000 may shut down with fatal access violations when you try to browse files in SQL Server 2000 Enterprise Manager on a Windows Server 2003 x64-based computer | August 2006 | |
| 8.0.2189 | 8.00.2189 | 2000.80.2189.0 | SP4 | KB916652 | FIX: An access violation may occur when you run a query on a table that has a multicolumn index in SQL Server 2000 | August 2006 | |
| 8.0.2189 | 8.00.2189 | 2000.80.2189.0 | SP4 | KB913438 | FIX: The SQL Server process may end unexpectedly when you turn on trace flag -T1204 and a profiler trace is capturing the Lock:DeadLock Chain event in SQL Server 2000 SP4 | July 2006 | |
| 8.0.2187 | 8.00.2187 | 2000.80.2187.0 | SP4 | KB915340 | FIX: A deadlock occurs when the scheduled SQL Server Agent job that you add or that you update is running in SQL Server 2000 | August 2006 | |
| 8.0.2039 | 8.00.2039 | 2000.80.2039.0 | SP4 | KB8E2DFC8D-C20E-4446-99A9-B7F0213F8BC5 | SQL Server 2000 Service Pack 4 (SP4) Latest SP | August 2005 | |
| … | … | … | … | … | … | … | |
| 8.0.194 | 8.00.194 | 2000.80.194 | RTM | SQL Server 2000 RTM (no SP) RTM | 2000 |
Microsoft SQL Server 7.0 Builds
SQL Server 7.0, codenamed “Sphinx”, was known for its user-friendliness and significant architectural changes, paving the way for modern SQL Server.
| Build | Alternative builds | File version | SP | CU | KB | KB / Description | Release Date |
|---|---|---|---|---|---|---|---|
| 7.0.1099 | 7.00.1099 | 9807.00.1099 | SP4 | Q321542 | KB321542 – SQL 7.0: Post-SP4 Hotfix, January 24, 2002 | Jan 2002 | |
| 7.0.1097 | 7.00.1097 | 9807.00.1097 | SP4 | Q321542 | KB321542 – SQL 7.0: Post-SP4 Hotfix, January 24, 2002 | Jan 2002 | |
| 7.0.1095 | 7.00.1095 | 9807.00.1095 | SP4 | Q317391 | KB317391 – FIX: Error Message When You Run a Query Against a Table with a Text Column | Aug 2001 | |
| 7.0.1089 | 7.00.1089 | 9807.00.1089 | SP4 | Q311483 | KB311483 – FIX: Access Violation When You Perform Data Transformation Services Tasks | May 2001 | |
| 7.0.1088 | 7.00.1088 | 9807.00.1088 | SP4 | Q304448 | KB304448 – FIX: Error Message When You Run a Query That Contains the “BETWEEN” Predicate | Feb 2001 | |
| 7.0.1087 | 7.00.1087 | 9807.00.1087 | SP4 | Q302981 | KB302981 – FIX: Access Violation When You Run a Query That Contains a Correlated Subquery | Jan 2001 | |
| 7.0.1085 | 7.00.1085 | 9807.00.1085 | SP4 | Q297880 | KB297880 – FIX: Error Message When You Run a Query That Contains a Correlated Subquery | Nov 2000 | |
| 7.0.1083 | 7.00.1083 | 9807.00.1083 | SP4 | Q295385 | KB295385 – FIX: Error Message When You Run a Query That Contains a Correlated Subquery | Sep 2000 | |
| 7.0.1063 | 7.00.1063 | 9807.00.1063 | SP4 | KB7959 | SQL Server 7.0 Service Pack 4 (SP4) Latest SP | Aug 2000 | |
| 7.0.1058 | 7.00.1058 | 9807.00.1058 | SP3 | Q321542 | KB321542 – SQL 7.0: Post-SP4 Hotfix, January 24, 2002 | Jan 2002 | |
| 7.0.1057 | 7.00.1057 | 9807.00.1057 | SP3 | Q321542 | KB321542 – SQL 7.0: Post-SP4 Hotfix, January 24, 2002 | Jan 2002 | |
| 7.0.1055 | 7.00.1055 | 9807.00.1055 | SP3 | Q317391 | KB317391 – FIX: Error Message When You Run a Query Against a Table with a Text Column | Aug 2001 | |
| 7.0.1049 | 7.00.1049 | 9807.00.1049 | SP3 | Q311483 | KB311483 – FIX: Access Violation When You Perform Data Transformation Services Tasks | May 2001 | |
| 7.0.1048 | 7.00.1048 | 9807.00.1048 | SP3 | Q304448 | KB304448 – FIX: Error Message When You Run a Query That Contains the “BETWEEN” Predicate | Feb 2001 | |
| 7.0.1047 | 7.00.1047 | 9807.00.1047 | SP3 | Q302981 | KB302981 – FIX: Access Violation When You Run a Query That Contains a Correlated Subquery | Jan 2001 | |
| 7.0.1045 | 7.00.1045 | 9807.00.1045 | SP3 | Q297880 | KB297880 – FIX: Error Message When You Run a Query That Contains a Correlated Subquery | Nov 2000 | |
| 7.0.1043 | 7.00.1043 | 9807.00.1043 | SP3 | Q295385 | KB295385 – FIX: Error Message When You Run a Query That Contains a Correlated Subquery | Sep 2000 | |
| 7.0.961 | 7.00.961 | 9807.00.0961 | SP3 | KB9c71f91c-a88f-4d31-9e8b-9fd63fbdbdcf | SQL Server 7.0 Service Pack 3 (SP3) Latest SP | Jun 2000 | |
| 7.0.950 | 7.00.950 | 9807.00.0950 | SP2 | Q321542 | KB321542 – SQL 7.0: Post-SP4 Hotfix, January 24, 2002 | Jan 2002 | |
| 7.0.949 | 7.00.949 | 9807.00.0949 | SP2 | Q321542 | KB321542 – SQL 7.0: Post-SP4 Hotfix, January 24, 2002 | Jan 2002 | |
| 7.0.947 | 7.00.947 | 9807.00.0947 | SP2 | Q317391 | KB317391 – FIX: Error Message When You Run a Query Against a Table with a Text Column | Aug 2001 | |
| 7.0.941 | 7.00.941 | 9807.00.0941 | SP2 | Q311483 | KB311483 – FIX: Access Violation When You Perform Data Transformation Services Tasks | May 2001 | |
| 7.0.940 | 7.00.940 | 9807.00.0940 | SP2 | Q304448 | KB304448 – FIX: Error Message When You Run a Query That Contains the “BETWEEN” Predicate | Feb 2001 | |
| 7.0.939 | 7.00.939 | 9807.00.0939 | SP2 | Q302981 | KB302981 – FIX: Access Violation When You Run a Query That Contains a Correlated Subquery | Jan 2001 | |
| 7.0.937 | 7.00.937 | 9807.00.0937 | SP2 | Q297880 | KB297880 – FIX: Error Message When You Run a Query That Contains a Correlated Subquery | Nov 2000 | |
| 7.0.935 | 7.00.935 | 9807.00.0935 | SP2 | Q295385 | KB295385 – FIX: Error Message When You Run a Query That Contains a Correlated Subquery | Sep 2000 | |
| 7.0.842 | 7.00.842 | 9807.00.0842 | SP2 | KBC4C935C7-4429-4172-9D54-C8A60927F372 | SQL Server 7.0 Service Pack 2 (SP2) Latest SP | Jun 1999 | |
| 7.0.830 | 7.00.830 | 9807.00.0830 | SP1 | Q321542 | KB321542 – SQL 7.0: Post-SP4 Hotfix, January 24, 2002 | Jan 2002 | |
| 7.0.829 | 7.00.829 | 9807.00.0829 | SP1 | Q321542 | KB321542 – SQL 7.0: Post-SP4 Hotfix, January 24, 2002 | Jan 2002 | |
| 7.0.827 | 7.00.827 | 9807.00.0827 | SP1 | Q317391 | KB317391 – FIX: Error Message When You Run a Query Against a Table with a Text Column | Aug 2001 | |
| 7.0.821 | 7.00.821 | 9807.00.0821 | SP1 | Q311483 | KB311483 – FIX: Access Violation When You Perform Data Transformation Services Tasks | May 2001 | |
| 7.0.820 | 7.00.820 | 9807.00.0820 | SP1 | Q304448 | KB304448 – FIX: Error Message When You Run a Query That Contains the “BETWEEN” Predicate | Feb 2001 | |
| 7.0.819 | 7.00.819 | 9807.00.0819 | SP1 | Q302981 | KB302981 – FIX: Access Violation When You Run a Query That Contains a Correlated Subquery | Jan 2001 | |
| 7.0.817 | 7.00.817 | 9807.00.0817 | SP1 | Q297880 | KB297880 – FIX: Error Message When You Run a Query That Contains a Correlated Subquery | Nov 2000 | |
| 7.0.815 | 7.00.815 | 9807.00.0815 | SP1 | Q295385 | KB295385 – FIX: Error Message When You Run a Query That Contains a Correlated Subquery | Sep 2000 | |
| 7.0.699 | 7.00.699 | 9807.00.0699 | SP1 | KB3884A944-3363-43CD-99E9-031A93C04413 | SQL Server 7.0 Service Pack 1 (SP1) Latest SP | Aug 1999 | |
| 7.0.637 | 7.00.637 | 9807.00.0637 | RTM | Q238759 | KB238759 – FIX: Error Message When You Run a Query That Contains a Correlated Subquery | Dec 1999 | |
| 7.0.633 | 7.00.633 | 9807.00.0633 | RTM | Q238695 | KB238695 – FIX: Error Message When You Run a Query That Contains a Correlated Subquery | Dec 1999 | |
| 7.0.631 | 7.00.631 | 9807.00.0631 | RTM | Q237194 | KB237194 – FIX: Error Message When You Run a Query That Contains a Correlated Subquery | Nov 1999 | |
| 7.0.629 | 7.00.629 | 9807.00.0629 | RTM | Q236544 | KB236544 – FIX: Error Message When You Run a Query That Contains a Correlated Subquery | Nov 1999 | |
| 7.0.627 | 7.00.627 | 9807.00.0627 | RTM | Q235944 | KB235944 – FIX: Error Message When You Run a Query That Contains a Correlated Subquery | Nov 1999 | |
| 7.0.625 | 7.00.625 | 9807.00.0625 | RTM | Q235514 | KB235514 – FIX: Error Message When You Run a Query That Contains a Correlated Subquery | Nov 1999 | |
| 7.0.623 | 7.00.623 | 9807.00.0623 | RTM | SQL Server 7.0 RTM RTM | 1998 |
Microsoft SQL Server 6.5 Builds
SQL Server 6.5, codenamed “Hydra”, was a significant step forward, improving performance and ease of use compared to its predecessors.
| Build | Alternative builds | File version | SP | CU | KB | KB / Description | Release Date |
|---|---|---|---|---|---|---|---|
| SP5 6.50.416 | 6.50.416 | SP5 | SQL Server 6.5 Service Pack 5 (SP5) Latest SP | ||||
| SP4 6.50.281 | 6.50.281 | SP4 | SQL Server 6.5 Service Pack 4 (SP4) | ||||
| 6.50.258 | 6.50.258 | Hotfix | |||||
| 6.50.240 | 6.50.240 | Hotfix | |||||
| 6.50.213 | 6.50.213 | Hotfix | |||||
| 6.50.201 | 6.5.201 | RTM | SQL Server 6.5 RTM RTM | 1996 |
Microsoft SQL Server 6.0 Builds
SQL Server 6.0, codenamed “SQL95”, marked Microsoft’s entry into the 64-bit computing space and included substantial performance improvements.
| Build | Alternative builds | File version | SP | CU | KB | KB / Description | Release Date |
|---|---|---|---|---|---|---|---|
| 6.00.151 | 6.0.151 | Hotfix | |||||
| 6.00.139 | 6.0.139 | Hotfix | |||||
| 6.00.124 | 6.0.124 | Hotfix | |||||
| 6.00.121 | 6.0.121 | RTM | SQL Server 6.0 RTM RTM | 1995 |
Legend for Build Types:
| Abbreviation | Description |
|---|---|
| CTP | Community Technology Preview (beta release) |
| RC | Release Candidate |
| RTM | Released To Manufacturing; It is the original, released build version of the product, i.e. what you get on the DVD or when you download the ISO file from MSDN. |
| CU | Cumulative Update; Cumulative updates contain bug fixes and enhancements. Microsoft recommends ongoing, proactive installation of SQL Server CUs as they become available. SQL Server CUs are certified to the same levels as Service Packs. |
| SP | Service Pack; A large collection of hotfixes that have been fully regression tested. Service Packs are discontinued starting from SQL Server 2017. |
| GDR | General Distribution Release; GDR fixes are typically security-related and do not contain CU updates. |
| QFE | Quick Fix Engineering; QFE updates include CU fixes. (Often used interchangeably with Hotfix) |
| CVE | Common Vulnerabilities and Exposures; publicly known information-security vulnerabilities. |
| OD | On-Demand hotfix. Released per customer request for specific problem scenarios. |
| COD | Critical On-Demand hotfix. Critical due to security impact or severe stability/functionality issues. |
This SQL Server versions chart aims to be a continuously updated resource. If you find it helpful, consider supporting the site.
Buy me a coffee Support me in another way
© 2007–2025 SqlServerBuilds.blogspot.com · Contact · Privacy policy
Other useful sites › SQL Server Versions List · Firebird Database Versions List · Exchange Server Versions List · SharePoint Servers Version List · Microsoft Knowledge Base Monitoring
