Two SQL Server versions that still run a large share of business databases are at the end of the road. SQL Server 2016 left extended support on 14 July 2026, and SQL Server 2017 follows on 12 October 2027 (Microsoft lifecycle pages, read on 5 November 2026). Neither stops working on that day, which is exactly why they linger. This guide gives the lifecycle table for every version from 2014 to 2025, explains what "unsupported" costs in compliance terms, sets out the Extended Security Updates route and its conditions, and walks through the upgrade to SQL Server 2022 or 2025, including the edition decision that comes with it and the option of moving to a hosted SQL Server with the licence included.
The lifecycle table, 2014 to 2025
Dates are from Microsoft's lifecycle pages read on 5 November 2026. Microsoft lists each cut-off as 6:59 AM Pacific time on the following day; the conventional dates below are the ones Microsoft uses in its own announcements.
| Version | Released | Mainstream support ended | Extended support ends | Extended Security Updates |
|---|---|---|---|---|
| SQL Server 2014 | June 2014 | 9 July 2019 | 9 July 2024 | Three years, to July 2027 |
| SQL Server 2016 | June 2016 | 13 July 2021 | 14 July 2026 | Three years, to mid-July 2029 (paid, see below) |
| SQL Server 2017 | September 2017 | 11 October 2022 | 12 October 2027 | Not announced at the time of writing |
| SQL Server 2019 | November 2019 | 28 February 2025 | 8 January 2030 | Not applicable yet |
| SQL Server 2022 | November 2022 | 11 January 2028 | 11 January 2033 | Not applicable yet |
| SQL Server 2025 | 18 November 2025 | 6 January 2031 | 6 January 2036 | Not applicable yet |
Two details from the table shape the decision. SQL Server 2019 has less than four years of extended support left, so it is a poor upgrade target in 2026. And SQL Server 2022 is the last version with a Web edition: Microsoft's editions documentation states that Web edition is not available in SQL Server 2025 and later, while the free Express edition gains the Advanced Services features from 2025. If you run Web edition today, the Web edition guide explains what that means for your next upgrade.
What unsupported means for compliance
A database server past extended support receives no security updates unless it is enrolled in Extended Security Updates. Microsoft does not pre-announce fixes for unsupported versions; when a vulnerability in the database engine is disclosed, 2016 without ESU simply does not get the patch that 2019 and 2022 get the same day. The compliance frameworks that touch databases all react to that:
- PCI DSS requirement 6 requires known vulnerabilities to be patched and requirement 12 requires an inventory of components with an end-of-life review. An unsupported SQL Server holding cardholder data fails both without an assessor-approved compensating control.
- HIPAA requires a risk analysis and risk management process; an unpatched database holding electronic protected health information is a documented risk with no mitigation. The proposed Security Rule update adds explicit patching timelines.
- ISO 27001:2022 control A.8.8, technical vulnerability management, expects unsupported software to be identified and dealt with, and auditors ask for the register.
- Cyber-insurance questionnaires increasingly ask whether any system runs end-of-life software, and a yes raises the premium or voids the cover.
There is also the practical side. Current SQL Server Management Studio, drivers and monitoring agents drop old versions on their own schedules, and every modern application framework targets the TLS and authentication behaviour of current releases. Running old SQL Server gets harder every quarter, not just riskier.
Extended Security Updates: what they cost and require
Microsoft offers ESUs for SQL Server 2014 and 2016 (its ESU page, read on 5 November 2026). The conditions changed with 2016:
- ESUs are delivered through Azure Arc. You connect the on-premises or hosted instance to Azure Arc (free) and subscribe, either with Software Assurance under an Enterprise, Server and Cloud or Education agreement, or on a pay-as-you-go basis billed hourly through Azure without SA.
- Unlike SQL Server 2014, moving a SQL Server 2016 instance to an Azure virtual machine does not give free ESUs; 2016 customers subscribe and pay there too.
- ESUs cover updates rated Critical by the Microsoft Security Response Center, released as needed, and include the latest cumulative update. No new features, no non-security fixes, and support is limited to installing the updates themselves.
- Instances that cannot connect to Azure Arc may be able to buy ESUs through volume licensing and register them manually; Microsoft says to contact the account team.
ESUs are a bridge, priced to encourage you to cross it. For most teams the cost of a year of ESU subscription is comparable to the work of the upgrade, and the upgrade is the one you have to do anyway. Use ESUs for the one instance whose application vendor has not certified a newer SQL Server, and upgrade the rest.
The upgrade path: in place or side by side
Microsoft supports an in-place upgrade to SQL Server 2022 from SQL Server 2012 SP4, 2014 SP3, 2016 SP3, 2017 and 2019 (Microsoft's supported upgrades page, read on 5 November 2026). SQL Server 2016 must therefore be on Service Pack 3 before Setup will upgrade it. Edition is preserved or raised, never lowered: Standard upgrades to Standard or Enterprise, Web to Web, Standard or Enterprise, Express to any edition.
A side-by-side migration (new server, backup and restore) is the better choice in almost every case, for four reasons: the old server stays intact as the fallback, you can change the operating system and hardware at the same time, you can change edition and licensing model in one step, and you rehearse the whole thing before the cut-over. The procedure:
- Inventory. Run Microsoft's Data Migration Assistant against the old instance. It lists deprecated features, breaking changes and behaviour changes per compatibility level, and it is the document you take to the application vendor.
- Build the target. Install SQL Server 2022 or 2025 on Windows Server 2025 with the same collation as the source (check
SELECT SERVERPROPERTY('Collation')), the same instance name if the application hard-codes it, and the same SQL Server Agent jobs, linked servers and logins (script them withsp_help_revloginor the dbatoolsCopy-DbaLogincommand so passwords and SIDs survive). - Rehearse. Take a full backup, restore it on the new server with
RESTORE DATABASE ... WITH RECOVERY, and point a test copy of the application at it. Fix what breaks. Do this at least twice. - Cut over. Stop the application, take a tail-log backup, restore it, set the database to the new compatibility level (160 for 2022, 170 for 2025), run
DBCC CHECKDB, thensp_updatestatsor a full statistics update, because the new cardinality estimator uses the statistics differently. Enable Query Store before go-live so you can compare plans. - Watch. Keep the compatibility level at the old value for the first week if you are nervous (SQL Server 2022 on compatibility level 130 behaves like 2016 for query optimisation), then raise it and use Query Store to force any plan that regressed.
A backup taken on SQL Server 2008 or later restores on SQL Server 2022 as long as the database compatibility level is 100 or higher, so even very old databases move this way. Log shipping from the old instance to the new one is supported and gives you a near-zero-downtime cut-over for large databases.
Choosing the edition after the upgrade
The upgrade is the one moment the edition decision is free, because you are re-licensing anyway. The capacity limits are Microsoft's SQL Server 2022 figures.
| Edition | Compute and memory | Choose it when | Licence route |
|---|---|---|---|
| Express | 4 cores, 1,410 MB buffer pool, 10 GB per database | Small databases, test and development, embedded applications | Free |
| Web | 16 cores, 64 GB | Public websites, SaaS and APIs; not internal applications; not available after 2022 | Rented from a hosting provider under SPLA |
| Standard | 24 cores, 128 GB | Line-of-business, ERP, internal reporting, Basic Availability Groups | Own it with Software Assurance, or rent under SPLA |
| Enterprise | Operating-system maximum | Full availability groups, online index operations, very large or very busy databases | Own it, or rent under SPLA |
Most 2016 and 2017 Standard installations stay Standard. The question worth asking is whether to keep owning the licence. A licence with active Software Assurance can be brought to a hosting provider that is not one of Microsoft's Listed Providers under the Flexible Virtualization Benefit; a licence without SA cannot move to any shared host and is only good for your own hardware. The bring-your-own-licence guide covers the rules. If you are leaving your own hardware at the same time, renting the licence monthly removes the SA renewal and the audit exposure in one move.
Moving to a hosted SQL Server with the licence included
Side-by-side migration means the target server can be anywhere, so an end-of-support upgrade is the natural time to stop running the database on hardware you own. On a MassiveGRID SQL Server host the target is a Managed Cloud Dedicated Server with reserved vCores, ECC RAM and NVMe on a Proxmox HA cluster, with Windows Server Standard and the SQL Server Web edition licensed per vCore under our SPLA agreement: $33.25 per vCore, $2.00 per GB of RAM and $0.03 per GB of NVMe, so 2 vCores, 8 GB and 128 GB cost $86.34 a month and 4 vCores, 16 GB and 256 GB cost $172.68, in New York, London, Frankfurt or Singapore. Standard edition is bring-your-own under License Mobility or quoted; on the Virtual Private Cloud it is on the order form at $120.00 per vCore.
The management service covers what an end-of-support project usually exposes as unowned work: operating system patching, hardening, daily backups with snapshots, 24/7 monitoring and the HA failover that restarts the server on another node within about two minutes of a hardware failure. SQL Server installation is part of the build; database administration beyond the operating system is quoted per project, and migration of an existing database onto the server is done with our team at no extra cost. For a small database that has outgrown nothing, a Windows VPS with SQL Server Express is the budget route, from $3.99 a month, with the same 10 GB per-database limit Express always had.
Frequently Asked Questions
Is SQL Server 2016 still supported?
No. Extended support for SQL Server 2016 ended on 14 July 2026. Microsoft offers paid Extended Security Updates for it through Azure Arc, with Software Assurance or on a pay-as-you-go basis, for up to three years. Moving the instance to an Azure virtual machine does not give free ESUs for 2016, unlike 2014.
When does SQL Server 2017 end of support happen?
Extended support for SQL Server 2017 ends on 12 October 2027. Mainstream support ended on 11 October 2022. No Extended Security Updates programme for 2017 was published on Microsoft's ESU page as of 5 November 2026.
Can I upgrade SQL Server 2016 directly to SQL Server 2022?
Yes, in place from SQL Server 2016 Service Pack 3 or later, keeping or raising the edition. Microsoft also supports in-place upgrades to 2022 from 2012 SP4, 2014 SP3, 2017 and 2019. A side-by-side migration with backup and restore is usually safer and lets you change the operating system, edition and licensing at the same time.
Which version should I upgrade to, SQL Server 2022 or 2025?
SQL Server 2025 has the longest runway (mainstream support to January 2031, extended to January 2036) and is the default for a new build. Choose SQL Server 2022 if your application vendor has not certified 2025 or if you need Web edition, which does not exist in 2025. Avoid 2019 as a target; its extended support ends in January 2030.
Does the compatibility level change when I restore an old database on a new server?
No. A restored database keeps its compatibility level (for example 130 for a 2016 database) until you change it, so it behaves as before for query optimisation. Raise it to 160 or 170 after testing, update statistics, and use Query Store to catch regressions.
Upgrade onto a managed SQL Server host instead of new hardware
MassiveGRID installs SQL Server 2022 on a managed cloud dedicated server with reserved vCores, Windows Server Standard and SQL Server Web licensed per vCore under our SPLA agreement, daily backups, 24/7 monitoring and HA failover, from $86.34 a month in four cities. Bring a Standard licence with Software Assurance or ask for a quote, and let our team migrate the database at no extra cost.
Configure a SQL Server HostFurther Reading
- Microsoft Lifecycle: SQL Server 2016 (support dates and ESU years)
- Microsoft Lifecycle: SQL Server 2017
- Microsoft Lifecycle: SQL Server 2025
- Microsoft Learn: What are Extended Security Updates for SQL Server
- Microsoft Learn: Supported version and edition upgrades (SQL Server 2022)
- Microsoft Learn: Editions and supported features of SQL Server 2022