EOL.WikiEOL.Wiki
← ← Back to all products

Microsoft SQL ServerEnd of Life (EOL) Dates & Support Status

Active
DatabasesLatest Version: 17.0.5005.3 CU9Latest Release: Sep 15, 2026

Microsoft SQL Server is a relational database management system by Microsoft for enterprise data management.

CISA known-exploited vulnerability signal

CISA KEV catalog version 2026.09.25 includes 2 manually mapped record(s) for this product.

Newest matching record added: Aug 26, 2026

Open the CISA KEV catalog ↗

This is a product-level catalog match, not a finding that the version shown above is vulnerable. Review each vendor advisory and affected-version range before acting.

Matching CVEs (showing up to 2)

  • CVE-2019-1068
  • CVE-2020-0618

Support summary

Microsoft SQL Server has cycles in security-only maintenance. Production workloads should move toward actively supported releases.

What do EOL and support statuses mean?

Next EOL

Oct 12, 2027

Microsoft SQL Server 14.0 · 380 days left

Supported cycles

4

0 lts

Versions

36

Latest Version

17.0.5005.3 CU9

Active Support

2

EOL

32

Lifecycle Timeline

Nov 16, 2016As of Sep 27, 2026
17.0Active · Jan 6, 2036
16.0Active · Jan 11, 2033
13.0-sp3-acpEOL · Jul 14, 2026
13.0-sp3EOL · Jul 14, 2026
15.0Security · Jan 8, 2030
12.0-sp3EOL · Jul 9, 2024
13.0-sp2EOL · Oct 11, 2022
11.0-sp4EOL · Jul 12, 2022
14.0Security · Oct 12, 2027
13.0-sp1EOL · Jul 9, 2019
ActiveSecurityEOLHistorical phase unknown

Bars show history up to the snapshot date. Gray intervals lack dated support boundaries; arrows indicate an unannounced EOL date, not a support guarantee.

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
17.0SQL25Nov 18, 2025Jan 6, 2031Jan 6, 203617.0.5005.3 CU9No
Active
16.0DallasNov 16, 2022Jan 11, 2028Jan 11, 203316.0.4295.3 CU27No
Active
13.0-sp3-acpSQL16May 19, 2022Jul 14, 2026Jul 14, 202613.0.7095.1 Azure Connect pack+GDRNo
EOL
13.0-sp3SQL16Sep 15, 2021Jul 14, 2026Jul 14, 202613.0.6500.1 GDRNo
EOL
15.0Aris/SeattleNov 4, 2019Feb 28, 2025Jan 8, 203015.0.4490.9 CU32+GDRNo
Security
12.0-sp3HekatonOct 30, 2018Jul 9, 2019Jul 9, 202412.0.6449.1 CU4+GDRNo
EOL
13.0-sp2SQL16Apr 24, 2018Oct 11, 2022Oct 11, 202213.0.5893.48 CU17+GDRNo
EOL
11.0-sp4DenaliOct 5, 2017Jul 12, 2022Jul 12, 202211.0.7512.11 GDRNo
EOL
14.0HelsinkiSep 29, 2017Oct 11, 2022Oct 12, 202714.0.3550.4 CU31+GDRNo
Security
13.0-sp1SQL16Nov 16, 2016Jul 9, 2019Jul 9, 201913.0.4604.0 CU15+GDRNo
EOL
12.0-sp2HekatonJul 14, 2016Jan 14, 2020Jan 14, 202012.0.5687.1 CU18No
EOL
13.0SQL16Jun 1, 2016Jan 9, 2018Jan 9, 201813.0.2218.0 CU9+GDRNo
EOL
11.0-sp3DenaliDec 1, 2015Oct 9, 2018Oct 9, 201811.0.6614.2 CU10+QFENo
EOL
12.0-sp1HekatonApr 14, 2015Oct 10, 2017Oct 10, 201712.0.4522.0 CU13No
EOL
10.50-sp3KilimanjaroJul 7, 2014Jul 8, 2014Jul 9, 201910.50.6785.2 GDRNo
EOL
10.0-sp4KatmaiJul 7, 2014Jul 8, 2014Jul 9, 201910.0.6814.4 CU17+GDRNo
EOL
11.0-sp2DenaliJun 10, 2014Jan 10, 2017Jan 10, 201711.0.5678.0 CU16No
EOL
12.0HekatonJun 5, 2014Jul 12, 2016Jul 12, 201612.0.2569.0 CU14No
EOL
11.0-sp1DenaliNov 7, 2012Jul 14, 2015Jul 14, 201511.0.3513.0 CU13+QFENo
EOL
10.50-sp2KilimanjaroJul 26, 2012Oct 13, 2015Oct 13, 201510.50.4339.0 CU13+QFENo
EOL
11.0DenaliMay 20, 2012Jan 14, 2014Jan 14, 201411.0.2424.0 CU11No
EOL
10.00-sp3KatmaiOct 6, 2011Oct 13, 2015Oct 13, 201510.00.5861 CU16+QFENo
EOL
10.50-sp1KilimanjaroJul 12, 2011Oct 8, 2013Oct 8, 201310.50.2881.0 CU14No
EOL
9.0-sp4YukonDec 13, 2010Apr 12, 2011Apr 12, 20169.0.5324.0 QFENo
EOL
10.00-sp2KatmaiSep 24, 2010Oct 9, 2012Oct 9, 201210.00.4371 CU10+QFENo
EOL
10.50-r2KilimanjaroJul 20, 2010Jul 10, 2012Jul 10, 201210.50.1815.0 CU13No
EOL
10.00-sp1KatmaiMar 31, 2009Oct 11, 2011Oct 11, 201110.00.2850 CU16No
EOL
9.00-sp3YukonDec 15, 2008Jan 10, 2012Jan 10, 20129.00.4309 CU11No
EOL
10.00KatmaiNov 6, 2008Apr 13, 2010Apr 13, 201010.00.1835 CU10No
EOL
9.00-sp2YukonFeb 19, 2007Jan 12, 2010Jan 12, 20109.00.3325 CU13No
EOL
9.0-sp1YukonApr 18, 2006Apr 8, 2008Apr 8, 20089.0.2233No
EOL
9.0YukonJan 14, 2006Jul 10, 2007Jul 10, 20079.0.1399No
EOL
8.0-sp4ShilohMay 6, 2005Apr 8, 2008Apr 9, 20138.0.2305 QFENo
EOL
7.0-sp4SphinxApr 26, 2002Dec 31, 2005Jan 11, 20117.0.1152No
EOL
6.50-sp5aHydraDec 24, 1998Jan 1, 2002Jan 1, 20026.50.480No
EOL
6.0-sp3SQL95Jun 13, 1995Mar 31, 1999Mar 31, 19996.0.151No
EOL

Data sources

Embed this badge

Microsoft SQL Server end-of-life support status badge

Show Microsoft SQL Server's live support status in your README, docs, or dashboard. The badge is a static SVG served from eol.wiki and follows the lifecycle data above.

Markdown

[![Microsoft SQL Server end-of-life status](https://eol.wiki/badge/mssqlserver.svg)](https://eol.wiki/mssqlserver/)

HTML

<a href="https://eol.wiki/mssqlserver/"><img src="https://eol.wiki/badge/mssqlserver.svg" alt="Microsoft SQL Server end-of-life status" height="20"></a>
All badges & lifecycle API →

Frequently Asked Questions

Which versions of Microsoft SQL Server have reached end of life?
The following Microsoft SQL Server versions have reached end of life and no longer receive security updates: 13.0-sp3-acp, 13.0-sp3, 12.0-sp3, 13.0-sp2, 11.0-sp4, 13.0-sp1, 12.0-sp2, 13.0 (and 24 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Microsoft SQL Server 13.0-sp3-acp?
Microsoft SQL Server 13.0-sp3-acp has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Microsoft SQL Server?
The latest version of Microsoft SQL Server is 17.0.5005.3 CU9, released in the 17.0 release cycle.
How many versions of Microsoft SQL Server are currently supported?
Microsoft SQL Server currently has 4 actively supported version(s): 17.0, 16.0, 15.0, 14.0.
When does Microsoft SQL Server 17.0 reach end of life?
Microsoft SQL Server 17.0 is scheduled to reach end of life on Jan 6, 2036.
What should I do when Microsoft SQL Server reaches end of life?
When a Microsoft SQL Server version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.