Logo-Icon
HOMEABOUTSERVICESHOW WE WORKBLOGInstagram-Icon Talk To an Expert
RadixTrie-image
SQL Server 2016 end of support options
Architecture

SQL Server 2016 Is Out of Support: Your Options, Ranked

Microsoft's extended support for SQL Server 2016 ended in July 2026. If you still run it, here are the realistic options, what each involves, and how to choose without disrupting the business.
By RadixTrie3 September 20262 min read
SQL Server 2016 was a solid release, and a great many South African systems still run on it. That is now a problem. Microsoft's extended support for SQL Server 2016 ended in July 2026, which means no further security updates. Every month that passes adds risk, and the auditors and insurers who care about patch status will notice. This article ranks the realistic options so you can choose deliberately.

What out of support actually means

The database keeps working. Nothing switches off. What stops is the flow of security fixes for newly discovered vulnerabilities, and the ability to get vendor support for problems. In practice, that changes the risk profile of every system on that instance, and it tends to conflict with compliance frameworks, cyber insurance conditions and customer due-diligence questionnaires. It is a business risk decision, and it should be made consciously rather than by default.

The options, ranked

  1. Upgrade to a current version on your own infrastructure. SQL Server 2022 is the current mainstream release, with extended support running into 2033. A side-by-side migration to a new instance, with application testing and a planned cutover, is the cleanest route. It keeps your operating model and gives you the longest runway.
  2. Upgrade to SQL Server 2019 as a stepping stone. Sometimes application vendors have not yet certified 2022. SQL Server 2019 is supported until January 2030, so it buys years rather than months, but you will do this again.
  3. Move to Azure. Azure SQL Managed Instance removes version management entirely and suits estates that want to stop operating database servers. SQL Server on Azure virtual machines keeps full control while moving the hosting. Both change your cost model and need network, latency and licensing planning.
  4. Buy time with paid extended security updates. Microsoft has offered paid Extended Security Updates for out-of-support SQL Server versions, delivered through Azure Arc. Check current availability and pricing for 2016; this is a bridge to one of the options above, not a destination.
  5. Isolate and accept the risk. For a system that is genuinely being retired within months, network isolation, hardened access and a written risk acceptance can be reasonable. It is the worst option for anything that is staying.
Whichever option you choose, the first step is the same: an inventory of every 2016 instance, its edition, the applications that depend on it, and which of those applications are certified for a newer version.

How an upgrade actually goes

A well-run SQL Server upgrade is mostly preparation. Compatibility assessment of databases and application code. A test environment on the target version with production-like data. Query performance comparison, because plans change between versions and a handful of queries usually need attention. Agreement with application owners on the cutover window and rollback plan. Then a rehearsed migration, ideally using backup and restore or availability-group techniques that keep the old instance intact until the new one is proven. The technical work is well understood; the risk is in skipping the preparation.

Do not forget 2017 and 2019

SQL Server 2017 leaves extended support in October 2027 and SQL Server 2019 in January 2030. If you are planning an upgrade programme for 2016 now, include those instances in the roadmap so the estate converges on one or two supported versions rather than repeating the exercise every eighteen months.

How RadixTrie helps

RadixTrie's senior SQL Server engineers plan and run upgrades and migrations for South African organisations, from assessment through cutover, and then keep the estate healthy under our <a href="/services">support and managed DBA services</a>. Our article on <a href="/blog/sql-server-support-south-africa">what good SQL Server support looks like</a> covers the operating model that stops the next end-of-support deadline from being a surprise.
<strong>Related reading:</strong> <a href="/blog/sql-server-support-south-africa">SQL Server Support in South Africa: What Good Looks Like</a> &middot; <a href="/blog/high-availability-disaster-recovery">High Availability and Disaster Recovery: Tested Beats Configured</a> &middot; <a href="/blog/database-health-check">The Database Health Check: What a Good One Covers and What It Finds</a>
Still on SQL Server 2016? Let's map the options for your estate.
TAGSSQL ServerSQL Server 2016UpgradeMigrationSouth Africa
RadixTrie-image
SQL Server 2016 end of support options
Architecture

SQL Server 2016 Is Out of Support: Your Options, Ranked

Microsoft's extended support for SQL Server 2016 ended in July 2026. If you still run it, here are the realistic options, what each involves, and how to choose without disrupting the business.
By RadixTrie3 September 20262 min read
SQL Server 2016 was a solid release, and a great many South African systems still run on it. That is now a problem. Microsoft's extended support for SQL Server 2016 ended in July 2026, which means no further security updates. Every month that passes adds risk, and the auditors and insurers who care about patch status will notice. This article ranks the realistic options so you can choose deliberately.

What out of support actually means

The database keeps working. Nothing switches off. What stops is the flow of security fixes for newly discovered vulnerabilities, and the ability to get vendor support for problems. In practice, that changes the risk profile of every system on that instance, and it tends to conflict with compliance frameworks, cyber insurance conditions and customer due-diligence questionnaires. It is a business risk decision, and it should be made consciously rather than by default.

The options, ranked

  1. Upgrade to a current version on your own infrastructure. SQL Server 2022 is the current mainstream release, with extended support running into 2033. A side-by-side migration to a new instance, with application testing and a planned cutover, is the cleanest route. It keeps your operating model and gives you the longest runway.
  2. Upgrade to SQL Server 2019 as a stepping stone. Sometimes application vendors have not yet certified 2022. SQL Server 2019 is supported until January 2030, so it buys years rather than months, but you will do this again.
  3. Move to Azure. Azure SQL Managed Instance removes version management entirely and suits estates that want to stop operating database servers. SQL Server on Azure virtual machines keeps full control while moving the hosting. Both change your cost model and need network, latency and licensing planning.
  4. Buy time with paid extended security updates. Microsoft has offered paid Extended Security Updates for out-of-support SQL Server versions, delivered through Azure Arc. Check current availability and pricing for 2016; this is a bridge to one of the options above, not a destination.
  5. Isolate and accept the risk. For a system that is genuinely being retired within months, network isolation, hardened access and a written risk acceptance can be reasonable. It is the worst option for anything that is staying.
Whichever option you choose, the first step is the same: an inventory of every 2016 instance, its edition, the applications that depend on it, and which of those applications are certified for a newer version.

How an upgrade actually goes

A well-run SQL Server upgrade is mostly preparation. Compatibility assessment of databases and application code. A test environment on the target version with production-like data. Query performance comparison, because plans change between versions and a handful of queries usually need attention. Agreement with application owners on the cutover window and rollback plan. Then a rehearsed migration, ideally using backup and restore or availability-group techniques that keep the old instance intact until the new one is proven. The technical work is well understood; the risk is in skipping the preparation.

Do not forget 2017 and 2019

SQL Server 2017 leaves extended support in October 2027 and SQL Server 2019 in January 2030. If you are planning an upgrade programme for 2016 now, include those instances in the roadmap so the estate converges on one or two supported versions rather than repeating the exercise every eighteen months.

How RadixTrie helps

RadixTrie's senior SQL Server engineers plan and run upgrades and migrations for South African organisations, from assessment through cutover, and then keep the estate healthy under our <a href="/services">support and managed DBA services</a>. Our article on <a href="/blog/sql-server-support-south-africa">what good SQL Server support looks like</a> covers the operating model that stops the next end-of-support deadline from being a surprise.
<strong>Related reading:</strong> <a href="/blog/sql-server-support-south-africa">SQL Server Support in South Africa: What Good Looks Like</a> &middot; <a href="/blog/high-availability-disaster-recovery">High Availability and Disaster Recovery: Tested Beats Configured</a> &middot; <a href="/blog/database-health-check">The Database Health Check: What a Good One Covers and What It Finds</a>
Still on SQL Server 2016? Let's map the options for your estate.
TAGSSQL ServerSQL Server 2016UpgradeMigrationSouth Africa