SQL Server 2016 support ended: here is what to do now

What actually stopped on that date

Three things ended together: security updates for newly discovered vulnerabilities, bug fixes, and technical support from Microsoft. Nothing switches off. Connections still open, jobs still run. The difference is that from July 15 onward, every new critical vulnerability in the engine is permanent on that instance unless it is covered by Extended Security Updates. On a database, that is not an abstract concern: it is the layer auditors and cyber-insurers ask about first. See how unsupported software affects compliance and insurance.

Extended Security Updates, the paid bridge

If you genuinely cannot migrate yet, ESU keeps critical patches flowing. The terms are narrow on purpose.

ESU does not restore general support, deliver non-security fixes or turn 2016 back into a current release. It buys migration time, and the on-premises version is a paid subscription while an Azure move includes it at no extra charge.

Your options, honestly compared

• Upgrade in place to SQL Server 2022 or 2025. The straightforward long-term answer, and fully supported on your own infrastructure. Test application compatibility and deprecated features first, because a decade is long enough for both to have moved.
• Migrate to an Azure SQL option. Azure SQL Managed Instance or Azure SQL Database remove the patching problem entirely and include ESU on the way. Worth modelling when the underlying server is also aging.
• Buy Extended Security Updates. A bridge, not a home. Sensible for a workload with a certified dependency that cannot move yet, but the migration still has to happen before 2029.
• Retire the database. The forgotten option. Old SQL instances accumulate, and some exist only because nobody has asked. Confirm what still connects before you assume it is load-bearing.

How long a migration really takes

Database migrations are rarely limited by SQL Server itself. They are limited by the applications that connect to it, the queries that depend on deprecated behaviour, and the testing you need to trust the cutover. A simple migration is a two to three month project. A complex estate with tightly coupled applications is four to six months. Either way, "we still have ESU until 2029" is how a manageable project becomes an emergency in 2028.

Do not stop at the database

A SQL Server 2016 instance is usually running on Windows Server 2016, which leaves extended support on January 12, 2027, on hardware that is often near its own End of Service Life. That is three overlapping deadlines on one box. While you are planning the database move, capture the operating system and hardware end-of-support dates for the same server, so you solve them as one project rather than three. Treating all of it as one lifecycle management problem is what keeps these from stacking up.

Related deadlines worth noting

The 2016 platform generation is retiring together: Windows Server 2016 on January 12, 2027, and on the desktop Windows 10 already ended in October 2025. The full, continuously updated view sits on the IT end-of-support calendar.