Microsoft SQL Server 2019 'Aris/Seattle' · Version Status

Microsoft SQL Server 2019 'Aris/Seattle' End of Life Date

Microsoft SQL Server 2019 'Aris/Seattle' end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.

✓ Microsoft SQL Server 2019 'Aris/Seattle' is actively supported. EOL date: January 8, 2030.
📅 Get reminded before Microsoft SQL Server 2019 'Aris/Seattle' reaches EOL on January 8, 2030 — alerts 90, 30 & 7 days out.
Google →
✉️ Or get it by email — alerts at 90 / 60 / 30 / 7 days and on the day: Free · one-click unsubscribe in every email · no other mail, ever
EOL Date
Jan 8, 2030
1179 days remaining
Latest Release
15.0.4500.2 CU32+GDR
Standard release
Release Date
Nov 4, 2019
Microsoft SQL Server 2019 'Aris/Seattle' series
Spotted a date that disagrees with the vendor's own lifecycle page? Report it with the vendor's link → Every correction is published on the accuracy page.
Lifecycle detail

Microsoft SQL Server 15.0 was released on November 4, 2019 and support is scheduled to end on January 8, 2030 — a planned supported lifespan of 10 years and 2 months, longer than the 3 years and 3 months median for Microsoft SQL Server releases. Its most recent patch is 15.0.4500.2 CU32+GDR, published October 13, 2026.

← Microsoft SQL Server 2014 'Hekaton' SP3 All Microsoft SQL Server versions Microsoft SQL Server 2016 SP3 →
30 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
0/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
20/20 Named in CISA KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →  ·  View score card →
All Microsoft SQL Server Versions
VersionLatestEOL DateStatus
6.0 'SQL95' SP3 6.0.151 Mar 31, 1999 EOL
6.5 'Hydra' SP5a 6.50.480 Jan 1, 2002 EOL
7.0 'Sphinx' SP4 7.0.1152 Jan 11, 2011 EOL
2000 'Shiloh' SP4 8.0.2305 QFE Apr 9, 2013 EOL
2005 RTM 'Yukon' 9.0.1399 Jul 10, 2007 EOL
2005 'Yukon' SP1 9.0.2233 Apr 8, 2008 EOL
2005 'Yukon' SP2 9.00.3325 CU13 Jan 12, 2010 EOL
2008 RTM 'Katmai' 10.00.1835 CU10 Apr 13, 2010 EOL

What does Microsoft SQL Server 2019 'Aris/Seattle' end of life mean?

When Microsoft SQL Server 2019 'Aris/Seattle' reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.

The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Microsoft SQL Server 2019 'Aris/Seattle' past its EOL date creates a growing attack surface that a clean scan result does not rule out.

Migrate to Microsoft SQL Server 2025 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Microsoft SQL Server 2019 'Aris/Seattle' reach end of life?
Microsoft SQL Server 2019 'Aris/Seattle' reaches end of life on January 8, 2030. That is 1179 days remaining.
Is Microsoft SQL Server 2019 'Aris/Seattle' still supported?
Yes, Microsoft SQL Server 2019 'Aris/Seattle' is currently supported. The EOL date is January 8, 2030.
What should I upgrade to from Microsoft SQL Server 2019 'Aris/Seattle'?
The recommended upgrade from Microsoft SQL Server 2019 'Aris/Seattle' is Microsoft SQL Server 2025 — the latest actively supported version. Check the Microsoft SQL Server full timeline for all supported versions.
What are the security risks of running Microsoft SQL Server 2019 'Aris/Seattle' past EOL?
When Microsoft SQL Server 2019 'Aris/Seattle' reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Microsoft SQL Server should migrate immediately or implement compensating controls.
Deep Dive
Full guide
SQL Server 2019 End of Life: January 8, 2030 (Extended Support)
→
Full guide
SQL Server 2022 End of Life: January 11, 2033 (End of Support)
→
Full guide
SQL Server End of Life: Every Version, 2012 to 2025, Support End Dates
→
Full guide
SQL Server 2016 End of Life (EOL) and End of Support: July 14, 2026
→
Data from endoflife.date API · Generated at build time · How we source data →