Microsoft SQL Server End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Microsoft SQL Server versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Extended Support | Days | Status |
|---|---|---|---|---|---|---|
| 6.0 'SQL95' SP3 | 6.0.151 | Jun 13, 1995 | Mar 31, 1999 | — | 9993 days past EOL | EOL |
| 6.5 'Hydra' SP5a | 6.50.480 | Dec 24, 1998 | Jan 1, 2002 | — | 8986 days past EOL | EOL |
| 7.0 'Sphinx' SP4 | 7.0.1152 | Apr 26, 2002 | Jan 11, 2011 | — | 5689 days past EOL | EOL |
| 2000 'Shiloh' SP4 | 8.0.2305 QFE | May 6, 2005 | Apr 9, 2013 | — | 4870 days past EOL | EOL |
| 2005 'Yukon' | 9.0.1399 | Jan 14, 2006 | Jul 10, 2007 | — | 6970 days past EOL | EOL |
| 2005 'Yukon' SP1 | 9.0.2233 | Apr 18, 2006 | Apr 8, 2008 | — | 6697 days past EOL | EOL |
| 2005 'Yukon' SP2 | 9.00.3325 CU13 | Feb 19, 2007 | Jan 12, 2010 | — | 6053 days past EOL | EOL |
| 2008 'Katmai' | 10.00.1835 CU10 | Nov 6, 2008 | Apr 13, 2010 | — | 5962 days past EOL | EOL |
| 2005 'Yukon' SP3 | 9.00.4309 CU11 | Dec 15, 2008 | Jan 10, 2012 | — | 5325 days past EOL | EOL |
| 2008 'Katmai' SP1 | 10.00.2850 CU16 | Mar 31, 2009 | Oct 11, 2011 | — | 5416 days past EOL | EOL |
| 2008 'Kilimanjaro' R2 | 10.50.1815.0 CU13 | Jul 20, 2010 | Jul 10, 2012 | — | 5143 days past EOL | EOL |
| 2008 'Katmai' SP2 | 10.00.4371 CU10+QFE | Sep 24, 2010 | Oct 9, 2012 | — | 5052 days past EOL | EOL |
| 2005 'Yukon' SP4 | 9.0.5324.0 QFE | Dec 13, 2010 | Apr 12, 2016 | — | 3771 days past EOL | EOL |
| 2008 R2 'Kilimanjaro' SP1 | 10.50.2881.0 CU14 | Jul 12, 2011 | Oct 8, 2013 | — | 4688 days past EOL | EOL |
| 2008 'Katmai' SP3 | 10.00.5861 CU16+QFE | Oct 6, 2011 | Oct 13, 2015 | — | 3953 days past EOL | EOL |
| 2012 'Denali' | 11.0.2424.0 CU11 | May 20, 2012 | Jan 14, 2014 | — | 4590 days past EOL | EOL |
| 2008 R2 'Kilimanjaro' SP2 | 10.50.4339.0 CU13+QFE | Jul 26, 2012 | Oct 13, 2015 | — | 3953 days past EOL | EOL |
| 2012 'Denali' SP1 | 11.0.3513.0 CU13+QFE | Nov 7, 2012 | Jul 14, 2015 | — | 4044 days past EOL | EOL |
| 2014 'Hekaton' | 12.0.2569.0 CU14 | Jun 5, 2014 | Jul 12, 2016 | — | 3680 days past EOL | EOL |
| 2012 'Denali' SP2 | 11.0.5678.0 CU16 | Jun 10, 2014 | Jan 10, 2017 | — | 3498 days past EOL | EOL |
| 2008 'Katmai' SP4 | 10.0.6814.4 CU17+GDR | Jul 7, 2014 | Jul 9, 2019 | Jul 12, 2022 Extended Security Updates (ESU) (ended) |
2588 days past EOL | EOL |
| 2008 R2 'Kilimanjaro' SP3 | 10.50.6785.2 GDR | Jul 7, 2014 | Jul 9, 2019 | Jul 12, 2022 Extended Security Updates (ESU) (ended) |
2588 days past EOL | EOL |
| 2014 'Hekaton' SP1 | 12.0.4522.0 CU13 | Apr 14, 2015 | Oct 10, 2017 | — | 3225 days past EOL | EOL |
| 2012 'Denali' SP3 | 11.0.6614.2 CU10+QFE | Dec 1, 2015 | Oct 9, 2018 | — | 2861 days past EOL | EOL |
| 2016 | 13.0.2218.0 CU9+GDR | Jun 1, 2016 | Jan 9, 2018 | — | 3134 days past EOL | EOL |
| 2014 'Hekaton' SP2 | 12.0.5687.1 CU18 | Jul 14, 2016 | Jan 14, 2020 | — | 2399 days past EOL | EOL |
| 2016 SP1 | 13.0.4604.0 CU15+GDR | Nov 16, 2016 | Jul 9, 2019 | — | 2588 days past EOL | EOL |
| 2017 'Helsinki' | 14.0.3540.1 CU31+GDR | Sep 29, 2017 | Oct 12, 2027 | — | 429 days remaining | Active |
| 2012 'Denali' SP4 | 11.0.7512.11 GDR | Oct 5, 2017 | Jul 12, 2022 | Jul 8, 2025 Extended Security Updates (ESU) (ended) |
1489 days past EOL | EOL |
| 2016 SP2 | 13.0.5893.48 CU17+GDR | Apr 24, 2018 | Oct 11, 2022 | — | 1398 days past EOL | EOL |
| 2014 'Hekaton' SP3 | 12.0.6449.1 CU4+GDR | Oct 30, 2018 | Jul 9, 2024 | Jul 12, 2027 Extended Security Updates (ESU) |
761 days past EOL | EOL |
| 2019 'Aris/Seattle' | 15.0.4480.2 CU32+GDR | Nov 4, 2019 | Jan 8, 2030 | — | 1248 days remaining | Active |
| 2016 SP3 | 13.0.6500.1 GDR | Sep 15, 2021 | Jul 14, 2026 | Jul 17, 2029 Extended Security Updates (ESU) |
26 days past EOL | EOL |
| 2016 SP3 Azure Connect Pack | 13.0.7095.1 Azure Connect pack+GDR | May 19, 2022 | Jul 14, 2026 | Jul 17, 2029 Extended Security Updates (ESU) |
26 days past EOL | EOL |
| 2022 'Dallas' | 16.0.4265.3 CU26 | Nov 16, 2022 | Jan 11, 2033 | — | 2347 days remaining | Active |
| 2025 | 17.0.4065.4 CU7 | Nov 18, 2025 | Jan 6, 2036 | — | 3437 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/mssqlserver)
Microsoft Extended Security Updates (ESU) Timeline
Microsoft's official lifecycle data lists the following Extended Security Update windows. ESU is a paid program that delivers critical security patches only, after a version's mainstream and extended support have already ended — it does not include new features, non-security fixes, or technical support.
| Product | ESU Phase | ESU End Date |
|---|---|---|
| Microsoft SQL Server 2012 | Extended Security Update Year 3 | Jul 9, 2025 |
| Microsoft SQL Server 2012 | Extended Security Update Year 2 | Jul 10, 2024 |
| Microsoft SQL Server 2012 | Extended Security Update Year 1 | Jul 12, 2023 |
| SQL Server 2014 | Extended Security Updates Year 3 | Jul 13, 2027 |
| SQL Server 2014 | Extended Security Updates Year 2 | Jul 15, 2026 |
| SQL Server 2014 | Extended Security Updates Year 1 | Jul 9, 2025 |
| SQL Server 2016 | Extended Security Updates Year 3 | Jul 17, 2029 |
| SQL Server 2016 | Extended Security Updates Year 2 | Jul 18, 2028 |
| SQL Server 2016 | Extended Security Updates Year 1 | Jul 13, 2027 |
Source: Microsoft Lifecycle — official Microsoft data, supplementary to endoflife.date.
What does Microsoft SQL Server end of life mean for your organization?
When a version of Microsoft SQL Server reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Microsoft SQL Server should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Microsoft SQL Server reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Microsoft SQL Server versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Microsoft SQL Server has 32 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for Microsoft SQL Server exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.