
Short answer: SQL Server 2019 is not at end of life yet. Mainstream support ended on February 28, 2025, and extended support (security updates only) continues until January 8, 2030. SQL Server 2016 reached end of support on July 14, 2026, and SQL Server 2017 follows on October 12, 2027. If you are planning an upgrade, SQL Server 2022 is supported until January 11, 2033, and SQL Server 2025 is the newest release.
“SQL Server 2019 end of life” is a common search because mainstream support ended in early 2025, and many people read that as the end. It is not. This guide explains the SQL Server lifecycle, what changes in extended support, how SQL Server 2019 compares with 2022, and how to plan an upgrade without surprises.
SQL Server support dates at a glance
| Version | Mainstream support ended/ends | Extended support ends | Status in late 2026 |
|---|---|---|---|
| SQL Server 2014 | July 9, 2019 | July 9, 2024 (ESU year 2 to July 14, 2026) | Out of support |
| SQL Server 2016 | July 13, 2021 | July 14, 2026 | Out of support |
| SQL Server 2017 | October 11, 2022 | October 12, 2027 | Extended support |
| SQL Server 2019 | February 28, 2025 | January 8, 2030 | Extended support |
| SQL Server 2022 | January 11, 2028 | January 11, 2033 | Mainstream support |
| SQL Server 2025 | Newest release | See Microsoft lifecycle page | Mainstream support |
Confirm dates on Microsoft’s SQL Server 2019 lifecycle page and the 2026 end-of-support list.
Mainstream vs extended support: what changed for SQL Server 2019
During mainstream support Microsoft delivers cumulative updates with bug fixes, performance improvements and occasional new capabilities, plus security fixes.
In extended support, which SQL Server 2019 entered in March 2025:
- Security updates continue through January 8, 2030.
- Non-security cumulative updates stop (the final CUs were released around the end of mainstream support).
- No new features or design-change requests.
- Paid support remains available.
For a stable production database, extended support is acceptable. For a system that keeps hitting bugs or performance limits, it is a signal to plan an upgrade.
SQL Server 2019 vs SQL Server 2022: what you gain
| Area | SQL Server 2019 | SQL Server 2022 |
|---|---|---|
| Support end | January 8, 2030 | January 11, 2033 |
| Query performance | Intelligent Query Processing (first generation) | Parameter Sensitive Plan optimization, DOP and memory-grant feedback with persistence |
| Query Store | Opt-in | On by default for new databases |
| Security | Always Encrypted with secure enclaves | Ledger tables for tamper evidence, Azure AD (Microsoft Entra) authentication, granular permissions |
| High availability | Always On availability groups | Contained availability groups (logins and jobs move with the group) |
| Cloud integration | Limited | Link to Azure SQL Managed Instance, Azure Synapse Link, Microsoft Purview |
| Data virtualization | PolyBase with Hadoop | S3-compatible object storage and Parquet/Delta via OPENROWSET |
| Backup | Standard backup | Backup and restore to S3-compatible storage |
| Standard edition compute limit | Lesser of 4 sockets or 24 cores | Lesser of 4 sockets or 24 cores |
| Standard edition buffer pool memory | 128 GB | 128 GB |
Compute limits come from Microsoft’s compute capacity limits by edition page. SQL Server 2025 raises Standard edition to the lesser of 4 sockets or 32 cores.
Should you upgrade from SQL Server 2019 now?
Upgrade soon if:
- You need features only in 2022, such as contained availability groups or the Azure SQL Managed Instance link.
- You want the longest runway: SQL Server 2022 is supported three years longer.
- You are deploying new servers anyway (new hardware is the cheapest moment to upgrade).
- Your application vendor certifies SQL Server 2022.
Staying on 2019 is reasonable if:
- The database is stable and the vendor supports only 2019.
- You will replace or decommission the system before 2030.
- You are budgeting for a jump straight to SQL Server 2025.
How to upgrade from SQL Server 2019 to 2022
- Run Data Migration Assistant (or Azure Migrate’s SQL assessment) to detect breaking changes and deprecated features.
- Check application compatibility with the vendor.
- Back up all databases (including system databases) and test restores.
- Choose the method:
- In-place upgrade: run SQL Server 2022 setup on the existing server and choose “Upgrade from a previous version”. Simple, but rollback means restoring.
- Side-by-side migration: install SQL Server 2022 on a new server, then back up and restore or use log shipping/availability groups to cut over. Easier rollback.
- Keep the database compatibility level at 150 (SQL Server 2019) at first, then raise it to 160 after testing, so query behavior changes are controlled.
- Update statistics and monitor Query Store for regressions.
- Re-apply logins, jobs and linked servers if you migrated side by side.
SQL Server 2022 supports in-place upgrades from SQL Server 2012 SP4 and later, so even older instances can move directly.
Licensing considerations
SQL Server is licensed either per core (minimum four cores per physical processor or per virtual machine) or Server + CAL (Standard edition only). Licenses for one version do not automatically cover a newer version unless you have Software Assurance. Before upgrading, confirm:
- The edition you need (see SQL Server Standard vs Enterprise)
- The number of cores to license
- Whether Software Assurance rights such as license mobility or passive failover replicas apply
Vaneyo lists SQL Server 2022 Standard, SQL Server 2022 Enterprise and SQL Server 2019 Standard licenses. Check the license scope described on each product page against your core count before buying.
What about SQL Server 2016 and 2017?
SQL Server 2016 reached end of support on July 14, 2026, so it no longer receives security updates. Move those databases first. SQL Server 2017 has until October 12, 2027. Both can upgrade directly to SQL Server 2022.
How to check your SQL Server version and edition
Run this query in SQL Server Management Studio or Azure Data Studio:
SELECT SERVERPROPERTY(‘ProductVersion’) AS Version, SERVERPROPERTY(‘ProductLevel’) AS Level, SERVERPROPERTY(‘Edition’) AS Edition;
The major version number tells you the release: 15.x is SQL Server 2019, 16.x is SQL Server 2022, 14.x is 2017 and 13.x is 2016. The Edition column shows Standard, Enterprise, Developer or Express. Record the result for every instance in your environment; the inventory drives both your upgrade plan and your license count.
Planning timeline for a SQL Server 2019 upgrade
| Phase | Activities | Typical duration |
|---|---|---|
| Discovery | Inventory instances, versions, editions, databases and dependent applications | 1 to 2 weeks |
| Assessment | Data Migration Assistant, vendor certification, licensing review | 1 to 2 weeks |
| Test | Restore copies on SQL Server 2022, run application tests, compare performance | 2 to 4 weeks |
| Cutover | Final backup or synchronization, switch connection strings, monitor | 1 day per instance |
| Optimization | Raise compatibility level, tune with Query Store | Ongoing |
Spreading the work over a quarter lets you upgrade during low-traffic periods and keeps rollback simple.
Does extended support matter for compliance?
Security frameworks such as PCI DSS, HIPAA risk assessments and SOC 2 audits generally expect supported, patched software. SQL Server 2019 in extended support still receives security patches, so it normally meets that expectation until January 2030 as long as you install the updates. SQL Server 2016 no longer does, which is why it should be your first priority.
Developer and Express editions
SQL Server Developer edition is free and includes all Enterprise features, but it is licensed only for development and testing, never production. SQL Server Express is free for production with limits: one socket or four cores, about 1.4 GB of buffer pool memory and 10 GB per database. Small applications sometimes run on Express; when they outgrow it, Standard is the usual next step.
Key terms explained
- Mainstream support: the first phase of Microsoft’s Fixed Lifecycle, with security updates, bug fixes and occasional improvements.
- Extended support: the second phase, with security updates only; for SQL Server 2019 it runs until January 8, 2030.
- Cumulative update (CU): a package of fixes released regularly during mainstream support.
- Compatibility level: a database setting (150 for SQL Server 2019, 160 for 2022) that controls query-processing behavior independently of the engine version.
- Extended Security Updates (ESU): a paid program that sometimes extends security patches beyond extended support for specific versions.
Common mistakes
- Treating the end of mainstream support as end of life. SQL Server 2019 gets security updates until 2030.
- Raising the compatibility level immediately after upgrading and then chasing query regressions.
- Forgetting SSIS, SSRS and SSAS. Reporting Services and Integration Services packages need their own testing.
- Licensing too few cores in virtual machines; each VM needs at least four core licenses.
- Upgrading without a tested restore.
Final takeaway
SQL Server 2019 is in extended support, not at end of life: you have security updates until January 2030. Use the time to plan. If you are deploying new hardware, need contained availability groups or want the longest runway, move to SQL Server 2022 now. Prioritize any remaining SQL Server 2016 instances, which are already out of support.
Frequently asked questions
Is SQL Server 2019 end of life?
No. SQL Server 2019 left mainstream support on February 28, 2025, but extended support with security updates continues until January 8, 2030.
When does SQL Server 2022 support end?
SQL Server 2022 mainstream support ends on January 11, 2028 and extended support ends on January 11, 2033.
Can I upgrade SQL Server 2019 to 2022 in place?
Yes. SQL Server 2022 setup supports an in-place upgrade from SQL Server 2019. Many teams prefer a side-by-side migration to a new server because it allows easier rollback.
What is new in SQL Server 2022 compared with 2019?
Key additions include Parameter Sensitive Plan optimization, Query Store on by default, ledger tables, contained availability groups, the link to Azure SQL Managed Instance and S3-compatible object storage integration.
Is SQL Server 2016 still supported?
No. SQL Server 2016 reached end of support on July 14, 2026 and no longer receives security updates.
