SQL Server 2016 End of Support: ESU Terms, Dates and Your Options

The short answer

SQL Server 2016 reached end of support on 14 July 2026. Mainstream support ended on 13 July 2021, and extended support, which delivered security updates only, ended five years later. Microsoft no longer ships security updates for SQL Server 2016 unless you subscribe to Extended Security Updates (ESUs), which run for up to three years, to 17 July 2029, and include Critical updates only. Service Pack 3 was the final service pack.

The server keeps running. What has stopped is the fix supply. The options are to upgrade, move to Azure SQL, pay for ESUs while you plan, or move to another database.

SQL Server 2016 lifecycle dates

Source: the Microsoft Lifecycle page for SQL Server 2016 and the SQL Server ESU FAQ. SQL Server 2016 follows the Fixed Lifecycle Policy, which gives each version at least ten years: five of mainstream support and five of extended support.

What end of support means for SQL Server 2016

• No security updates without ESUs. Vulnerabilities found after 14 July 2026 are not fixed in any public SQL Server 2016 update.
• No Microsoft technical support for the product, apart from the limited help that comes with an ESU subscription and a qualifying support plan.
• Compliance findings. An unsupported database engine is a finding under most control frameworks unless you can show a compensating control.
• Nothing breaks on the day. Licences stay valid, the service keeps running and applications keep connecting.

How SQL Server 2016 Extended Security Updates work

Microsoft calls ESUs "a last resort paid option" and "a temporary bridge" to a supported platform. The terms, from Microsoft's ESU documentation:

• Scope. Security updates rated Critical by the Microsoft Security Response Center, for up to three years. No new features, functional improvements or customer-requested fixes, and no regular release cadence: an update ships only when a Critical vulnerability needs one.
• Baseline. ESU packages include the most recent cumulative update. If you applied only GDR updates during support, Microsoft advises installing and validating the latest CU when you subscribe.
• Where you can get them. On Azure VMs through the SQL IaaS Agent extension, on Azure VMware Solution and Azure Stack, and everywhere else, including on premises and other clouds, by connecting the server to Azure Arc. Servers that cannot connect to Arc can be registered in disconnected mode after buying ESUs through volume licensing.
• Licensing. On premises you need Software Assurance or subscription licences under a qualifying agreement, or a pay-as-you-go subscription through Azure Arc. SQL Server 2014 instances moved to Azure VMs received ESUs through Windows Update without a subscription; SQL Server 2016 instances on Azure VMs have to subscribe like any other.
• Billing. Azure bills ESUs hourly. Enrol late and you are back-billed to the end-of-support date: Microsoft's example is a 2016 customer who enrols in January 2027 and is billed for July to December 2026.
• Support. ESU licences do not include support for SQL Server 2016 itself. Help is limited to deploying, installing and activating the updates, and only under one of the support plans Microsoft lists.

SQL Server 2016 end of support planning: your options

1. Upgrade to a current SQL Server version

SQL Server 2025 supports an upgrade from SQL Server 2016 SP3 or later, so most 2016 servers can move in one step. SQL Server 2022 and 2025 both have mainstream support into 2028 and 2031 respectively. Test with the target compatibility level and Query Tuning Assistant before the cutover.

2. Move to Azure SQL

Azure SQL Managed Instance and Azure SQL Database are, in Microsoft's words, managed services that "never reach end of support". Managed Instance is the closer match for a lift and shift. This changes how you run the database as well as where.

3. Subscribe to ESUs while you plan

Sensible when the upgrade or migration needs more than a few months. Treat the three years as a deadline, not a plan, and remember coverage is Critical updates only.

4. Move to PostgreSQL

For applications you own, an end-of-support date is a natural point to leave SQL Server licensing behind. T-SQL, temporary tables, identity columns and the many ways applications connect make it a real project. The SQL Server to PostgreSQL migration guide covers pgloader, a T-SQL rewrite and Babelfish.

Where OSSeva fits

OSSeva does not support or patch SQL Server, so for an in-place upgrade or ESUs, Microsoft and its partners are the right route. If you decide to leave, OSSeva's SQL Server to PostgreSQL offer assesses each application, moves the data, runs old and new side by side, and supports the PostgreSQL cluster from cutover onwards on infrastructure you control, priced per cluster. The database support cost calculator uses your own figures; book a discovery call for a quote.

Frequently asked questions

When is SQL Server 2016 end of support?

14 July 2026. Mainstream support ended on 13 July 2021, and extended support ended on 14 July 2026.

Is SQL Server 2016 end of life?

Yes, in the sense most people mean: Microsoft's support lifecycle for it ended on 14 July 2026. The only security updates after that date are ESUs, which run to 17 July 2029.

What are SQL Server 2016 ESUs?

A paid subscription that delivers Critical security updates for up to three years after end of support, through Azure, Azure Arc or volume licensing. It does not include new features, non-security fixes or general product support.

Do I need Azure to get SQL Server 2016 ESUs?

Not to run SQL Server in Azure. Servers on premises or in other clouds subscribe through Azure Arc, and servers that cannot connect can be registered in disconnected mode after a volume licensing purchase.

Can I upgrade SQL Server 2016 directly to SQL Server 2025?

Yes, from SQL Server 2016 SP3 or later.

What happens if we enrol in ESUs late?

Microsoft back-bills to the end-of-support date, so a January 2027 enrolment is charged from July 2026.