// OSSeva Blog
OperationsSQL Server 2019 End of Support: Mainstream Has Ended, Extended Runs to January 2030
The short answer
SQL Server 2019 reaches end of support on 8 January 2030. Mainstream support already ended on 28 February 2025, so SQL Server 2019 is in extended support, which Microsoft describes as including only security updates. Functional, performance and scalability fixes have stopped. After 8 January 2030, security updates stop as well.
SQL Server 2019 lifecycle dates
| Milestone | Date |
|---|---|
| Release | 4 November 2019 |
| End of mainstream support | 28 February 2025 |
| End of extended support | 8 January 2030 |
| Big Data Clusters retired | 28 February 2025 |
Source: the Microsoft Lifecycle page for SQL Server 2019, which applies to all editions on Windows and Linux, and Microsoft's lists of products ending support in 2025 and 2030.
What mainstream support ending already changed
Microsoft's lifecycle splits each version into five years of mainstream support, with functional, performance, scalability and security updates, and five years of extended support, with security updates only. Since 28 February 2025, a bug in SQL Server 2019 that is not a security issue no longer qualifies for a public fix. If you need a fix for a performance or correctness problem, look for it in a newer version. SQL Server Big Data Clusters, which shipped with 2019, were retired on the same day.
What changes on 8 January 2030
- Security updates stop, unless Microsoft announces an ESU programme for 2019. As of October 2026, its ESU FAQ lists only SQL Server 2014 and 2016.
- Microsoft product support ends.
- Instances still on 2019 become audit findings under most frameworks.
That is a little over three years from now. Upgrades and migrations across a large estate take time to test, so the date to plan around is earlier than January 2030.
Your options
1. Upgrade to SQL Server 2022 or 2025
Both accept upgrades from SQL Server 2019. SQL Server 2025 has mainstream support to January 2031 and extended support to January 2036; SQL Server 2022 has mainstream support to 11 January 2028. For most estates that stay on SQL Server, 2025 gives the longer runway.
2. Move to Azure SQL
Azure SQL Managed Instance and Azure SQL Database have no version end dates of their own; Microsoft says they never reach end of support. The trade is a managed platform in place of servers you run.
3. Move to PostgreSQL
If SQL Server licensing is a growing cost and you own the application code, the years before 2030 are enough to migrate without a deadline rush. The SQL Server to PostgreSQL migration guide compares a native rewrite, pgloader and Babelfish.
Where OSSeva fits
OSSeva does not support or patch SQL Server. For a version upgrade, staying with Microsoft is usually the simpler path. For applications that move off SQL Server, OSSeva's SQL Server to PostgreSQL offer covers the migration and supports PostgreSQL afterwards on your own infrastructure, under one contract with the rest of your open source data stack, priced per cluster. Try the database support cost calculator with your own numbers, or book a discovery call for a quote.
Frequently asked questions
When is SQL Server 2019 end of support?
8 January 2030, the end of extended support.
Has SQL Server 2019 mainstream support ended?
Yes, on 28 February 2025. SQL Server 2019 now receives security updates only.
What is the SQL Server 2019 end of service date?
Microsoft uses "end of support". For SQL Server 2019 that is 8 January 2030, after which no further updates ship.
Will there be ESUs for SQL Server 2019?
Microsoft has not announced any as of October 2026. Its ESU programmes so far cover SQL Server 2014 and 2016.
Which SQL Server version should we upgrade 2019 to?
SQL Server 2025 has the longest support window, with extended support to January 2036. SQL Server 2022 is the other supported target.
Tags
Ready to get your open source under control?
Talk to an OSSeva engineer about CVE coverage, compliance, and migration support for your stack.