dotNewLABS

Guides

SQL Server 2016 end of support: what healthcare and finance teams should do now

Published 22 October 2026 · dotNew Labs

SQL Server 2016 reached the end of extended support on July 14, 2026. It still runs, but new security fixes now come only through paid Extended Security Updates. For databases that hold patient or financial records, that needs a decision and a date.

2024202520262027202820292030203120322033SQL 2016ended 14 Jul 2026SQL 2017ends Oct 2027SQL 2019ends Jan 2030SQL 2022ends Jan 2033SQL 2025newest releaseToday
Extended support end dates by version. Bars that reach the right edge run past 2033 or end later.

Where your versions stand

VersionStatus
SQL Server 2014 and olderOut of support
SQL Server 2016Out of extended support since July 14, 2026
SQL Server 2017Extended support ends October 2027
SQL Server 2019, 2022, 2025Supported

Always confirm dates on Microsoft's lifecycle pages for your exact edition.

Your three options

What usually breaks in an upgrade

A safe order

  1. Inventory instances, databases, jobs, reports and the apps that connect.
  2. Restore a copy on the new version and run the assessment tools.
  3. Test the busiest and most important queries, and reconcile key report totals.
  4. Rehearse the cutover and the rollback, then schedule the window.

Don't forget the apps

An old database usually sits under an old application. If the app is on .NET Framework or WebForms, plan both together, so you change connection settings and test once instead of twice.

Not sure where your apps stand?

We offer a free 20-minute scan of one app: what it runs on, what's risky, and the shortest safe path forward. You keep a short written summary whether or not you hire us.

Book a free scan

Or email contact@dotnewlabs.ai

More guides