Your last SQL Server end-of-support deadline
Move a workload to Azure SQL properly and it never joins the upgrade queue again, says Johan Lamberts, MD at Ascent Technology.
Every SQL Server deadline results in a single project delivering no new functionalities. A team scoping an SQL Server 2016 project focuses on maintaining status quo, ensuring applications and reports function as before. Months of discovery, regression testing, and vendor certification are invested, but the outcome remains unchanged.
South African enterprises have repeatedly run this project since 2008, and it remains unnamed in business cases. This recurring program of work funded to maintain existing systems is likened to a tax collected by the version life cycle. The end of support for SQL Server 2016 on 14 July signifies the next invoice. Windows Server 2016, the operating system for many databases, also reaches end of support on 12 January 2027, followed by SQL Server 2017 in October 2027.
Each deadline triggers the same standstill project, consuming engineering capacity and delaying progress. Microsoft's Extended Security Updates (ESUs) for SQL Server 2016 are now chargeable at full license cost per year, with back-billing starting from the year the ESU year begins. This arrangement ends on 7 July 2029, leaving estates with no supported option.
The strategic decision matters more than financial figures; Microsoft has priced inaction now. An upgrade to SQL Server 2025 is recommended for organizations still on 2016, but migration involves assessing the applicability of workloads to versionless tiers like Azure SQL Managed Instance and Azure SQL Database. These platforms continuously provide updates, eliminating the need for version upgrades and ESUs.
The assessment process determines which workloads should remain on the version life cycle and which can benefit from the versionless tiers. One Microsoft Direct Cloud Solution Provider (CSP) offers a migration service that assesses workloads, implements a governed migration, and handles licensing and Azure consumption to ensure a seamless transition.
The 2016 deadline has already passed, but the next two deadlines are approaching. The choice for a 2016 estate is between running the final standstill project deliberately or funding the next one by default. The question is not whether migration can be afforded; it is how many more standstill projects the organization intends to fund.
Written by urgent.news from ITWeb's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.