PSG
Urgent help Talk to us
DEEN
Reference

SQL Server versions: builds, updates and end of support.

Which build is current, how far behind is your server, and how long will security updates still be available? We check this overview against Microsoft regularly and add what we observe in projects.

Last updated 29 Sep 2026Maturity growingChanges 1 entry ↓
SQL Server 2025CU917.0.5005.3 · 15 Sep 2026Mainstream supportSQL Server 2022CU2716.0.4295.3 · 15 Sep 2026Mainstream supportSQL Server 2019CU32 + GDR15.0.4490.9 · 8 Sep 2026Extended supportSQL Server 2017CU31 + GDR14.0.3550.4 · 8 Sep 2026Extended support
Tool

Which build is this?

In three steps, see which update is installed, how many have been released since, and how long Microsoft will continue to support the version.

  • The evaluation runs entirely in your browser.
  • Nothing is sent or stored.

01Run the commandin SSMS, Azure Data Studio or sqlcmd

SELECT @@VERSION;

02Paste the outputor just the build number

Example:

03ResultFor the data as of date, see above

The result appears here once you have pasted something.

All versions

Current status by version

Latest build according to Microsoft and the support dates. Click a version to see its complete update list.

VersionLatest buildSupported untilStatus today
SQL Server 2025Version 17.0 · compatibility level 170CU917.0.5005.3 · 15 Sep 2026Mainstream6 Jan 2031Extended6 Jan 2036Mainstream support
SQL Server 2022Version 16.0 · compatibility level 160CU2716.0.4295.3 · 15 Sep 2026Mainstream11 Jan 2028Extended11 Jan 2033Mainstream support
SQL Server 2019Version 15.0 · compatibility level 150CU32 + GDR15.0.4490.9 · 8 Sep 2026Mainstream28 Feb 2025Extended8 Jan 2030Extended support
SQL Server 2017Version 14.0 · compatibility level 140CU31 + GDR14.0.3550.4 · 8 Sep 2026Mainstream11 Oct 2022Extended12 Oct 2027Extended support
SQL Server 2016Version 13.0 · compatibility level 130Azure Connect Pack + GDR13.0.7095.1 · 14 Jul 2026Mainstream13 Jul 2021Extended14 Jul 2026No support
SQL Server 2014Version 12.0 · compatibility level 120CU4 + GDR12.0.6449.1 · 10 Oct 2023Mainstream9 Jul 2019Extended9 Jul 2024No support
SQL Server 2012Version 11.0 · compatibility level 110GDR for SP411.0.7512.11 · 14 Feb 2023Mainstream11 Jul 2017Extended12 Jul 2022No support
SQL Server 2008 R2Version 10.50 · compatibility level 100GDR Security Update10.50.6785.2 · 14 Feb 2023Mainstream8 Jul 2014Extended9 Jul 2019No support
SQL Server 2008Version 10.0 · compatibility level 100GDR for SP410.0.6814.4 · 14 Feb 2023Mainstream8 Jul 2014Extended9 Jul 2019No support
SQL Server 2005Version 9.00 · compatibility level 90MS12-070: QFE Security Update9.00.5324 · 9 Oct 2012Mainstream12 Apr 2011Extended12 Apr 2016No support
Lifecycle

How long will updates continue?

During mainstream support, Microsoft delivers cumulative updates with bug fixes. During extended support, only security updates are provided. After that there is nothing, except through paid Extended Security Updates, where Microsoft offers them.

Lifecycle of SQL Server versionsBars per version from release to the end of extended support; dark: mainstream support, light: extended support, line “today” at 29 Sep 2026.200520102015202020252030203520252022201920172016201420122008 R220082005▲ supported▼ unsupportedtoday

Mainstream support Extended support Extended Security Updates (paid) today

Perspective from projects

What we say about this in projects

  • There have been no service packs since SQL Server 2017.
    Microsoft delivers cumulative updates (CUs) with bug fixes, alongside security-only updates (GDR). If you stay on the GDR branch, you get security fixes but none of the bug fixes from the CUs.
  • Current does not mean on the day of release.
    A fixed cadence with a test environment is better than chance. What matters is that the backlog does not grow over the years. Otherwise every later update becomes a project.
  • A version change does not have to make things faster.
    Whether an upgrade helps with a performance problem depends on the workload. Some queries benefit from new optimizer features; others get different plans, which can also be worse, for example because of a new compatibility level. We check this beforehand rather than hoping. How we find root causes · One query, many plans.
  • End of support does not come as a surprise.
    The dates are set years in advance. An upgrade with testing, high availability and a rollback path needs lead time; we plan it with you.
Maintenance

Change log and sources

This page is part of our reference collection. Unlike an article, it is maintained: every substantive change is listed here with its date.

  1. Page rebuilt: all builds from SQL Server 2005 to 2025 checked against Microsoft Learn (page date 15 Sep 2026), build checker and a page per version added.

Sources

No guarantee for the information provided. The linked pages from Microsoft are authoritative. Microsoft and SQL Server are trademarks of the Microsoft group of companies.

Back to Knowledge