What ended on 14 July 2026
SQL Server follows Microsoft's fixed lifecycle: five years of mainstream support and five years of extended support. For SQL Server 2016 both periods are now over. Since 14 July 2026 there are no more security fixes, no other fixes and no technical support for SQL Server 2016, even if you have a support contract. Auditors and cyber insurers ask about this, and new drivers and tools gradually drop it.
Extended Security Updates: buying time until July 2029
Microsoft sells Extended Security Updates (ESU) for SQL Server 2016 until 17 July 2029. They are a bridge, not a solution:
- ESUs only contain security updates rated Critical by the Microsoft Security Response Center, released only when such a vulnerability is found. No other fixes, no new features.
- Only Enterprise and Standard edition qualify. Express, Web and Developer edition do not.
- The instance must run the latest service pack, SQL Server 2016 SP3.
- On your own servers or at another provider, the instance must be connected to Azure Arc. You then pay either through Software Assurance (Enterprise Agreement and similar programmes) or pay-as-you-go per core per hour, without Software Assurance.
- Unlike SQL Server 2014, SQL Server 2016 does not get free ESUs on Azure virtual machines: there you subscribe and pay as well.
- Billing started on 15 July 2026. If you subscribe later, Microsoft charges back to the start of the ESU term.
Upgrade paths
SQL Server 2016 SP3 can be upgraded in place to SQL Server 2019, 2022 or 2025. A backup of a SQL Server 2016 database can also be restored on any of these versions, on a new server; the old server then remains available as a fallback. The database keeps compatibility level 130 after the restore, so most code behaves as before until you raise the level.
Which target? SQL Server 2019 is supported until 8 January 2030, so it only buys a few years. SQL Server 2022 is supported until 11 January 2033 and SQL Server 2025 until 6 January 2036. For a database that should last, 2022 or 2025 is the sensible choice; check what your application vendor and tools support.
Cloud options
- Azure SQL Managed Instance: almost complete compatibility with SQL Server, including SQL Server Agent and cross-database queries, with patching done by Microsoft.
- Azure SQL Database: versionless and fully managed, but one database at a time: no SQL Server Agent, no cross-database queries.
- SQL Server on an Azure virtual machine: a newer SQL Server version on a VM you control; or SQL Server 2016 as is, with paid ESUs.
- Amazon RDS for SQL Server: AWS ended support for SQL Server 2016 on RDS on 14 July 2026 and schedules remaining instances for an automatic upgrade to SQL Server 2019. Upgrade yourself at a time that suits you, preferably straight to 2022 or 2025.
What to check before the move
The jump from 2016 to 2022 or 2025 is moderate, but check a few things: Stretch Database is discontinued, newer client drivers encrypt connections by default and check the server certificate, and logins, Agent jobs and linked servers do not move with a database backup. For Azure SQL the list of unsupported features is longer, for example file access from T-SQL and, for SQL Database, cross-database queries.
How the free scan helps
The MigrateMyDatabase scan runs a read-only script on your SQL Server 2016 database that collects the structure and which features your code uses. Paste the result in the page and compare SQL Server 2022 or 2025, Azure SQL Managed Instance, Azure SQL Database and Amazon RDS side by side, with a list of what needs attention per target. The analysis runs in your browser; the script reads no table data.
Questions
Does SQL Server 2016 stop working after 14 July 2026?
No. It keeps running exactly as before. What stops are security updates and support from Microsoft, unless you pay for Extended Security Updates.
Until when can I get ESUs for SQL Server 2016?
Until 17 July 2029, at most three years after the end of extended support. After that there are no more updates of any kind.
Are ESUs for SQL Server 2016 free on Azure?
No. SQL Server 2014 received free ESUs on Azure virtual machines, but for SQL Server 2016 you subscribe and pay, on Azure as well as on your own servers through Azure Arc.
Can I go from SQL Server 2016 straight to SQL Server 2025?
Yes. SQL Server 2025 supports an in-place upgrade from SQL Server 2016 SP3, and a SQL Server 2016 backup can be restored on SQL Server 2025.
See what your SQL Server 2016 database needs for SQL Server 2022, 2025 or Azure: run the read-only script, paste the result and compare the targets. Free, and nothing leaves your browser.
Start the free scan