This is the reference I keep open for every SQL Server environment I touch. One page with the latest build for every version from 2012 to 2025, what each build number means, and exactly when each version falls out of support.
Everything here is pulled from the official Microsoft build tables and the Microsoft Lifecycle pages, never from memory. Each version section below links its sources.
Latest Builds at a Glance
The build to be on is the latest Cumulative Update for your version. Where the CU train has closed, the security build column is the one that moves.
| Version | Latest CU | Latest Security Build | Support | Extended Ends |
|---|---|---|---|---|
| SQL Server 2025 | CU817.0.4075.5KB5104822, 13 August 2026 | CU6 + GDR17.0.4060.2KB5101346, 14 July 2026 | Mainstream | 6 January 2036 |
| SQL Server 2022 | CU2616.0.4265.3KB5093420, 16 July 2026 | CU25 + GDR16.0.4262.2KB5101347, 14 July 2026 | Mainstream | 11 January 2033 |
| SQL Server 2019 | CU32 (final CU)15.0.4430.1KB5054833, 27 February 2025 | CU32 + GDR15.0.4480.2KB5102335, 14 July 2026 | Extended | 8 January 2030 |
| SQL Server 2017 | CU31 (final CU)14.0.3456.2KB5016884, 20 September 2022 | CU31 + GDR14.0.3540.1KB5102337, 14 July 2026 | Extended | 12 October 2027 |
| SQL Server 2016 | SP2 CU17 (final CU)13.0.5888.11KB5001092, 29 March 2021 | SP3 + Azure Connect GDR13.0.7095.1KB5102339, 14 July 2026 | Out of support · ESU | 14 July 2026 |
| SQL Server 2014 | SP3 CU4 (final CU)12.0.6329.1KB4500181, 29 July 2019 | SP3 CU4 + GDR12.0.6449.1KB5029185, 10 October 2023 | Out of support · ESU | 9 July 2024 |
| SQL Server 2012 | SP3 CU10 (final CU)11.0.6607.3KB4025925, 8 August 2017 | SP4 GDR11.0.7512.11KB5021123, 14 February 2023 | Out of support | 12 July 2022 |
Note: Service Packs ended with SQL Server 2016. From SQL Server 2017 onward there are only Cumulative Updates and GDR security releases.
How to Read a Build Number
A SQL Server build number like 16.0.4265.3 breaks down as major version . minor . build . revision. The major number maps to the product version: 17 is SQL Server 2025, 16 is 2022, 15 is 2019, 14 is 2017, 13 is 2016, 12 is 2014 and 11 is 2012. The third part is the one to watch, since it moves with every CU and GDR.
Two servicing trains matter. The CU train (build numbers in the 4000s) carries all fixes and is what most environments should follow. The GDR train (always a lower build number than the CU train for the same version) carries security fixes only, for servers that deliberately never take CUs. Once you install a CU you are on the CU train and stay there.
To see where an instance sits right now:
SELECT SERVERPROPERTY('ProductVersion') AS build,
SERVERPROPERTY('ProductLevel') AS level,
SERVERPROPERTY('ProductUpdateLevel') AS cu,
SERVERPROPERTY('Edition') AS edition;
For a fleet-wide view against this list, my Get Patch Level script does the mapping for every instance you run it on.
Version Details
SQL Server 2025
Mainstream extended support until 6 January 2036
| RTM build | 17.0.1000.7, released 18 November 2025 |
| Latest CU | CU817.0.4075.5KB5104822, 13 August 2026 |
| Latest CU-train security build | CU6 + GDR17.0.4060.2KB5101346, 14 July 2026 |
| Latest GDR-train security build | GDR (RTM security train)17.0.1125.2KB5102333, 14 July 2026 |
| Mainstream support | ends 6 January 2031 |
| Extended support | ends 6 January 2036 |
| Native compatibility level | 170 (supports 170, 160, 150, 140, 130, 120, 110, 100) |
Current release. First version offering Standard Developer edition alongside Enterprise-based Developer.
Sources: SQL Server 2025 build versions (Microsoft Learn) · SQL Server 2025 lifecycle (Microsoft Lifecycle). Accessed 15 August 2026.
SQL Server 2022
Mainstream extended support until 11 January 2033
| RTM build | 16.0.1000.6, released 16 November 2022 |
| Latest CU | CU2616.0.4265.3KB5093420, 16 July 2026 |
| Latest CU-train security build | CU25 + GDR16.0.4262.2KB5101347, 14 July 2026 |
| Latest GDR-train security build | GDR (RTM security train)16.0.1190.2KB5102334, 14 July 2026 |
| Mainstream support | ends 11 January 2028 |
| Extended support | ends 11 January 2033 |
| Native compatibility level | 160 (supports 160, 150, 140, 130, 120, 110, 100) |
The most widely deployed current version. Still receiving regular CUs.
Sources: SQL Server 2022 build versions (Microsoft Learn) · SQL Server 2022 lifecycle (Microsoft Lifecycle). Accessed 15 August 2026.
SQL Server 2019
Extended ends 8 January 2030
| RTM build | 15.0.2000.5, released 4 November 2019 |
| Latest CU | CU32 (final CU)15.0.4430.1KB5054833, 27 February 2025 |
| Latest CU-train security build | CU32 + GDR15.0.4480.2KB5102335, 14 July 2026 |
| Latest GDR-train security build | GDR (RTM security train)15.0.2180.2KB5102336, 14 July 2026 |
| Mainstream support | ended 28 February 2025 |
| Extended support | ends 8 January 2030 |
| Native compatibility level | 150 (supports 150, 140, 130, 120, 110, 100) |
Mainstream support ended 28 February 2025. CU32 was the final cumulative update; patching now means the CU32 + GDR security builds.
Sources: Latest updates and version history (Microsoft Learn) · SQL Server 2019 lifecycle (Microsoft Lifecycle). Accessed 15 August 2026.
SQL Server 2017
Extended ends 12 October 2027
| RTM build | 14.0.1000.169, released 29 September 2017 |
| Feature pack | Azure Connect feature pack14.0.3490.10KB5050533, 6 March 2025 |
| Latest CU | CU31 (final CU)14.0.3456.2KB5016884, 20 September 2022 |
| Latest CU-train security build | CU31 + GDR14.0.3540.1KB5102337, 14 July 2026 |
| Latest GDR-train security build | GDR (RTM security train)14.0.2120.1KB5102338, 14 July 2026 |
| Mainstream support | ended 11 October 2022 |
| Extended support | ends 12 October 2027 |
| Native compatibility level | 140 (supports 140, 130, 120, 110, 100) |
In extended support until 12 October 2027. Security fixes still ship as CU31 + GDR builds.
Sources: Latest updates and version history (Microsoft Learn) · SQL Server 2017 lifecycle (Microsoft Lifecycle). Accessed 15 August 2026.
SQL Server 2016
Out of support · ESU since 14 July 2026
| RTM build | 13.0.1601.5, released 1 June 2016 |
| Latest Service Pack | SP313.0.6300.2KB5003279, 15 September 2021 |
| Feature pack | SP3 + Azure Connect feature pack13.0.7000.253KB5014242, 19 May 2022 |
| Latest CU | SP2 CU17 (final CU)13.0.5888.11KB5001092, 29 March 2021 |
| Latest GDR-train security build | SP3 + Azure Connect GDR13.0.7095.1KB5102339, 14 July 2026 |
| Latest SP3 GDR (no feature pack) | SP3 GDR13.0.6500.1KB5102340, 14 July 2026 |
| Mainstream support | ended 13 July 2021 |
| Extended support | ended 14 July 2026 |
| Extended Security Updates | ESU Year 1 runs 2026-07-15 to 2027-07-13; Year 3 ends 2029 |
| Native compatibility level | 130 (supports 130, 120, 110, 100) |
Extended support ended 14 July 2026. No more free security updates; Extended Security Updates (paid, or free in Azure) are the only patch path. July 2026 GDRs were the final regular updates.
Sources: Latest updates and version history (Microsoft Learn) · SQL Server 2016 lifecycle (Microsoft Lifecycle). Accessed 15 August 2026.
SQL Server 2014
Out of support · ESU since 9 July 2024
| RTM build | 12.0.2000.8, released 1 April 2014 |
| Latest Service Pack | SP312.0.6024.0KB4022619, 30 October 2018 |
| Latest CU | SP3 CU4 (final CU)12.0.6329.1KB4500181, 29 July 2019 |
| Latest CU-train security build | SP3 CU4 + GDR12.0.6449.1KB5029185, 10 October 2023 |
| Latest GDR-train security build | SP3 GDR12.0.6179.1KB5029184, 10 October 2023 |
| Mainstream support | ended 9 July 2019 |
| Extended support | ended 9 July 2024 |
| Extended Security Updates | ESU Year 3 runs 2026-07-15 to 2027-07-12 |
| Native compatibility level | 120 (supports 120, 110, 100) |
Extended support ended 9 July 2024. Last free security update was the October 2023 GDR. ESU coverage (paid, or free in Azure) runs to mid-2027.
Sources: Latest updates and version history (Microsoft Learn) · SQL Server 2014 lifecycle (Microsoft Lifecycle). Accessed 15 August 2026.
SQL Server 2012
Out of support since 12 July 2022
| RTM build | 11.0.2100.60, released 6 March 2012 |
| Latest Service Pack | SP411.0.7001.0KB4018073, 4 October 2017 |
| Latest CU | SP3 CU10 (final CU)11.0.6607.3KB4025925, 8 August 2017 |
| Latest GDR-train security build | SP4 GDR11.0.7512.11KB5021123, 14 February 2023 |
| Mainstream support | ended 11 July 2017 |
| Extended support | ended 12 July 2022 |
| Extended Security Updates | ESU program ended 2025-07-08 (Year 3) |
| Native compatibility level | 110 (supports 110, 100, 90) |
Fully out of support, including ESU. The February 2023 SP4 GDR is the last update that will ever ship.
Sources: Latest updates and version history (Microsoft Learn) · SQL Server 2012 lifecycle (Microsoft Lifecycle). Accessed 15 August 2026.
Frequently Asked Questions
How do I check which build my SQL Server is on?
Run SELECT SERVERPROPERTY('ProductVersion') and match the result against the tables above. The version check post walks through the other places the build number shows up.
What is the difference between a CU and a GDR?
A Cumulative Update contains every fix so far, functional and security. A GDR (General Distribution Release) contains security fixes only. Microsoft runs the two as separate trains: stay on GDR only if your change policy genuinely forbids CUs, otherwise take the CU train and get the bug fixes too.
Are Cumulative Updates really cumulative?
Yes. The latest CU includes everything from all earlier CUs for that version, so a new server goes straight from RTM to the newest CU in one step. There is no need to chain updates.
What happened to Service Packs?
Service Packs ended with SQL Server 2016 (SP3 was its last). From SQL Server 2017 onward, servicing is Cumulative Updates plus GDR security releases only.
My version is out of support. What are my options?
Three realistic paths: upgrade to a supported version, buy Extended Security Updates where the program still runs (2014 and 2016 as of the data-checked date, 2012 has ended), or move the workload to Azure where ESUs are included. My upgrade readiness script is the place to start planning.
How current is this page?
The data-checked date in the banner at the top is exact. The page is regenerated from Microsoft’s published build tables after each SQL Server patch release, normally within a few days of Patch Tuesday.
Sources
Primary sources, checked 15 August 2026:
- Latest updates and version history (Microsoft Learn)
Complete build tables (RTM/SP/CU/GDR + KB + release date) for every version, and the latest-updates summary table. - SQL Server 2025 build versions (Microsoft Learn)
SQL Server 2025 CU and GDR builds cross-check (doc dated 2026-08-13). - SQL Server 2022 build versions (Microsoft Learn)
SQL Server 2022 CU and GDR builds cross-check (doc dated 2026-07-16). - ALTER DATABASE compatibility level (Microsoft Learn)
Native (default) compatibility level and supported compat range per version.
If you spot a build I have missed, leave a comment and I will verify it against the Microsoft tables and add it.
The build ladder on this page is what the sqldba MCP server answers from. Its check_build tool turns a build number, a version year or a pasted @@VERSION string into the CU, the KB and the support dates, which is the one kind of answer that goes stale fastest when an AI works from memory.
Related
- How to Check SQL Server Version, turning a build number into a release
- Get Patch Level, where every instance sits against this list
- Get Version Upgrade Readiness, what to check before moving off an unsupported build
- Version Upgrade Runbook, the cutover itself once the target is chosen
- Patch SQL Server, the one-shot script that applies the latest CU when this page says you are behind
Leave a Reply