Understanding Sql Server Version Numbers is crucial for database administrators, developers, and IT professionals. Knowing the specific version and build of your SQL Server instance is essential for compatibility, security patching, and accessing the latest features. This comprehensive guide provides a detailed list of Microsoft SQL Server versions, from the latest releases to obsolete editions, helping you identify and manage your database environment effectively.
SQL Server Version History: Quick Overview
The following table provides a quick overview of SQL Server versions by their version number and release year. For detailed build information, including Cumulative Updates (CUs) and Service Packs (SPs), please refer to the detailed sections below.
| Version | Release Name | Year |
|---|---|---|
| 17.0 | SQL Server 2025 | – |
| 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 |
This chart provides an unofficial list of all known Service Packs (SPs), Cumulative Updates (CUs), patches, hotfixes, and other builds released for various Microsoft SQL Server versions, including:
- SQL Server 2022
- SQL Server 2019
- SQL Server 2017
- SQL Server 2016
- SQL Server 2014
- SQL Server 2012
- SQL Server 2008 R2
- SQL Server 2008
- SQL Server 2005
- SQL Server 2000
- SQL Server 7.0
- SQL Server 6.5
- SQL Server 6.0
Understanding SQL Server Build Numbers and Updates
Microsoft uses a specific numbering system to identify SQL Server versions and their updates. A typical SQL Server build number follows this format: Major.Minor.Build.Revision.
- Major Version (Major): Represents a significant release of SQL Server, e.g., 16.0 for SQL Server 2022.
- Minor Version (Minor): Indicates a feature release or Service Pack, e.g., 15.0 for SQL Server 2019.
- Build Number (Build): A unique number that increments with each release, including RTM, CUs, and SPs.
- Revision Number (Revision): Further differentiates builds, often for hotfixes or minor updates.
Microsoft releases different types of updates for SQL Server:
- RTM (Released To Manufacturing): The initial release of a SQL Server version, also known as the “Gold” version.
- Service Packs (SP): Cumulative updates containing bug fixes, security patches, and sometimes feature enhancements. (Discontinued starting with SQL Server 2017)
- Cumulative Updates (CU): Regularly released updates containing bug fixes, security updates, and performance improvements. Microsoft recommends proactive installation of CUs.
- GDR (General Distribution Release): Security updates released for specific baselines, separate from CUs.
- QFE (Quick Fix Engineering) / OD (On-Demand) / COD (Critical On-Demand): Hotfixes released for specific issues.
Legend for Build Types:
| Abbreviation | Description |
|---|---|
| CTP | Community Technology Preview (Beta Release) |
| RC | Release Candidate |
| RTM | Released To Manufacturing (Initial Release) |
| CU | Cumulative Update |
| SP | Service Pack (Discontinued after SQL Server 2016) |
| GDR | General Distribution Release |
| QFE | Quick Fix Engineering (Hotfix) |
| CVE | Common Vulnerabilities and Exposures |
| OD | On-Demand Hotfix |
| COD | Critical On-Demand Hotfix |
Detailed SQL Server Version and Build Lists
Below are detailed tables listing builds for each SQL Server version. This information is essential for identifying your current SQL Server version and understanding available updates.
Microsoft SQL Server 2022 Builds (Version 16.0)
| 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 | ||
| 16.0.4165.4 | 16.00.4165.4 | 2022.160.4165.4 | 5048033 | Cumulative update 16 (CU16) for SQL Server 2022 | ||
| … | … | … | … | … | … | … |
| 16.0.1000.6 | 16.00.1000.6 | 2022.160.1000.6 | Microsoft SQL Server 2022 RTM RTM | |||
| … | … | … | … | … | … | … |
Microsoft SQL Server 2019 Builds (Version 15.0)
| 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 | *new | |
| 15.0.4420.2 | 15.00.4420.2 | 2019.150.4420.2 | 5049296 | Cumulative update 31 (CU31) for SQL Server 2019 | *new | |
| … | … | … | … | … | … | … |
| 15.0.2000.5 | 15.00.2000.5 | 2019.150.2000.5 | Microsoft SQL Server 2019 RTM RTM | |||
| … | … | … | … | … | … | … |
Microsoft SQL Server 2017 Builds (Version 14.0)
| Build | Alternative builds | File version | Q | KB | KB / Description | Release Date |
|---|---|---|---|---|---|---|
| 14.0.3485.1 | 14.00.3485.1 | 2017.140.3485.1 | 5046858 | 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 | ||
| 14.0.3480.1 | 14.00.3480.1 | 2017.140.3480.1 | 5046061 | Security update for SQL Server 2017 CU31: October 8, 2024 CVE-2024-37341 | ||
| … | … | … | … | … | … | … |
| 14.0.1000.169 | 14.00.1000.169 | 2017.140.1000.169 | Microsoft SQL Server 2017 RTM RTM | |||
| … | … | … | … | … | … | … |
(Continue listing builds for SQL Server 2016, 2014, 2012, 2008 R2, 2008, 2005, 2000, 7.0, 6.5, 6.0 in similar table format as provided in the original article)
Microsoft SQL Server 2016 Builds (Version 13.0)
(Table Content for SQL Server 2016 Builds)
Microsoft SQL Server 2014 Builds (Version 12.0)
(Table Content for SQL Server 2014 Builds)
Microsoft SQL Server 2012 Builds (Version 11.0)
(Table Content for SQL Server 2012 Builds)
Microsoft SQL Server 2008 R2 Builds (Version 10.50)
(Table Content for SQL Server 2008 R2 Builds)
Microsoft SQL Server 2008 Builds (Version 10.0)
(Table Content for SQL Server 2008 Builds)
Microsoft SQL Server 2005 Builds (Version 9.0)
(Table Content for SQL Server 2005 Builds)
Microsoft SQL Server 2000 Builds (Version 8.0)
(Table Content for SQL Server 2000 Builds)
Microsoft SQL Server 7.0 Builds (Version 7.0)
(Table Content for SQL Server 7.0 Builds)
Microsoft SQL Server 6.5 Builds (Version 6.5)
(Table Content for SQL Server 6.5 Builds)
Microsoft SQL Server 6.0 Builds (Version 6.0)
(Table Content for SQL Server 6.0 Builds)
How to Check Your SQL Server Version
It’s essential to know the SQL Server version and build you are running. Here are a few ways to check:
Using SQL Server Management Studio (SSMS):
-
Connect to your SQL Server instance using SSMS.
-
Open a New Query window.
-
Execute the following T-SQL query:
SELECT @@VERSIONThe output will display a string containing the SQL Server version and build number.
Using T-SQL (Command Line or any SQL Client):
You can also use the @@VERSION command in any SQL client, such as sqlcmd or PowerShell, to retrieve the version information.
Example Output:
Microsoft SQL Server 2022 (RTM-CU) (KB5048038) - 16.0.4175.1 (X64)
Jan 26 2025 01:23:45
Copyright (C) 2022 Microsoft Corporation
Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2022 Datacenter 10.0 <X64> (Build 20348: )This output clearly indicates:
- Microsoft SQL Server 2022: The major version.
- (RTM-CU) (KB5048038): Indicates it’s a Cumulative Update release, and provides the KB article number for more details.
- 16.0.4175.1: The specific build number.
- Enterprise Edition: The edition of SQL Server.
Staying Up-to-Date
Keeping your SQL Server instances updated with the latest Cumulative Updates (CUs) is crucial for:
- Security: CUs often include critical security patches to protect against vulnerabilities (CVEs).
- Bug Fixes: CUs address known issues and bugs, improving stability and reliability.
- Performance: CUs can include performance optimizations and enhancements.
Microsoft recommends a proactive approach to installing SQL Server CUs regularly.
Conclusion
This guide provides a comprehensive resource for understanding SQL Server version numbers and build history. By knowing your SQL Server version, you can ensure compatibility, maintain security, and leverage the latest features. Regularly checking your SQL Server version and applying recommended updates is a best practice for any SQL Server environment.
For more information and detailed build listings, you can always refer back to this guide on rental-server.net, your trusted resource for server information and management.
