Complete end-of-life dates, support windows, and security status for all MS SQL Server versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 6.0-sp3 | 6.0.151 | Jun 13, 1995 | Mar 31, 1999 | 9901 days past EOL | EOL |
| 6.50-sp5a | 6.50.480 | Dec 24, 1998 | Jan 1, 2002 | 8894 days past EOL | EOL |
| 7.0-sp4 | 7.0.1152 | Apr 26, 2002 | Jan 11, 2011 | 5597 days past EOL | EOL |
| 8.0-sp4 | 8.0.2305 QFE | May 6, 2005 | Apr 9, 2013 | 4778 days past EOL | EOL |
| 9.0 | 9.0.1399 | Jan 14, 2006 | Jul 10, 2007 | 6878 days past EOL | EOL |
| 9.0-sp1 | 9.0.2233 | Apr 18, 2006 | Apr 8, 2008 | 6605 days past EOL | EOL |
| 9.00-sp2 | 9.00.3325 CU13 | Feb 19, 2007 | Jan 12, 2010 | 5961 days past EOL | EOL |
| 10.00 | 10.00.1835 CU10 | Nov 6, 2008 | Apr 13, 2010 | 5870 days past EOL | EOL |
| 9.00-sp3 | 9.00.4309 CU11 | Dec 15, 2008 | Jan 10, 2012 | 5233 days past EOL | EOL |
| 10.00-sp1 | 10.00.2850 CU16 | Mar 31, 2009 | Oct 11, 2011 | 5324 days past EOL | EOL |
| 10.50-r2 | 10.50.1815.0 CU13 | Jul 20, 2010 | Jul 10, 2012 | 5051 days past EOL | EOL |
| 10.00-sp2 | 10.00.4371 CU10+QFE | Sep 24, 2010 | Oct 9, 2012 | 4960 days past EOL | EOL |
| 9.0-sp4 | 9.0.5324.0 QFE | Dec 13, 2010 | Apr 12, 2016 | 3679 days past EOL | EOL |
| 10.50-sp1 | 10.50.2881.0 CU14 | Jul 12, 2011 | Oct 8, 2013 | 4596 days past EOL | EOL |
| 10.00-sp3 | 10.00.5861 CU16+QFE | Oct 6, 2011 | Oct 13, 2015 | 3861 days past EOL | EOL |
| 11.0 | 11.0.2424.0 CU11 | May 20, 2012 | Jan 14, 2014 | 4498 days past EOL | EOL |
| 10.50-sp2 | 10.50.4339.0 CU13+QFE | Jul 26, 2012 | Oct 13, 2015 | 3861 days past EOL | EOL |
| 11.0-sp1 | 11.0.3513.0 CU13+QFE | Nov 7, 2012 | Jul 14, 2015 | 3952 days past EOL | EOL |
| 12.0 | 12.0.2569.0 CU14 | Jun 5, 2014 | Jul 12, 2016 | 3588 days past EOL | EOL |
| 11.0-sp2 | 11.0.5678.0 CU16 | Jun 10, 2014 | Jan 10, 2017 | 3406 days past EOL | EOL |
| 10.0-sp4 | 10.0.6814.4 CU17+GDR | Jul 7, 2014 | Jul 9, 2019 | 2496 days past EOL | EOL |
| 10.50-sp3 | 10.50.6785.2 GDR | Jul 7, 2014 | Jul 9, 2019 | 2496 days past EOL | EOL |
| 12.0-sp1 | 12.0.4522.0 CU13 | Apr 14, 2015 | Oct 10, 2017 | 3133 days past EOL | EOL |
| 11.0-sp3 | 11.0.6614.2 CU10+QFE | Dec 1, 2015 | Oct 9, 2018 | 2769 days past EOL | EOL |
| 13.0 | 13.0.2218.0 CU9+GDR | Jun 1, 2016 | Jan 9, 2018 | 3042 days past EOL | EOL |
| 12.0-sp2 | 12.0.5687.1 CU18 | Jul 14, 2016 | Jan 14, 2020 | 2307 days past EOL | EOL |
| 13.0-sp1 | 13.0.4604.0 CU15+GDR | Nov 16, 2016 | Jul 9, 2019 | 2496 days past EOL | EOL |
| 14.0 | 14.0.3525.1 CU31+GDR | Sep 29, 2017 | Oct 12, 2027 | 521 days remaining | Active |
| 11.0-sp4 | 11.0.7512.11 GDR | Oct 5, 2017 | Jul 12, 2022 | 1397 days past EOL | EOL |
| 13.0-sp2 | 13.0.5893.48 CU17+GDR | Apr 24, 2018 | Oct 11, 2022 | 1306 days past EOL | EOL |
| 12.0-sp3 | 12.0.6449.1 CU4+GDR | Oct 30, 2018 | Jul 9, 2024 | 669 days past EOL | EOL |
| 15.0 | 15.0.4465.1 CU32+GDR | Nov 4, 2019 | Jan 8, 2030 | 1340 days remaining | Active |
| 13.0-sp3 | 13.0.6485.1 GDR | Sep 15, 2021 | Jul 14, 2026 | 66 days remaining | Warning |
| 13.0-sp3-acp | 13.0.7080.1 Azure Connect pack+GDR | May 19, 2022 | Jul 14, 2026 | 66 days remaining | Warning |
| 16.0 | 16.0.4250.1 CU24+GDR | Nov 16, 2022 | Jan 11, 2033 | 2439 days remaining | Active |
| 17.0 | 17.0.4035.5 CU4 | Nov 18, 2025 | Jan 6, 2036 | 3529 days remaining | Active |
When a MS SQL Server version 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 MS 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.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →