Architecture
SQL Server 2017 and 2019 End of Support: Dates, Risks and Your Options
SQL Server 2017 leaves extended support in October 2027 and SQL Server 2019 in January 2030. What each date means, what mainstream versus extended support actually changes, the risks of running past them, and the options ranked for South African estates.
By RadixTrie14 September 20263 min read
Every SQL Server version has two dates that matter and one that people confuse them with. Mainstream support is when Microsoft ships cumulative updates with fixes and improvements. Extended support is when only security updates ship. After extended support ends, nothing ships unless you pay for Extended Security Updates or move. SQL Server 2016 crossed that last line in July 2026. This article is about the two versions most South African estates are actually running, 2017 and 2019, what their dates mean and what to do about them in the right order.
The dates
- SQL Server 2016: extended support ended 14 July 2026. Already unsupported.
- SQL Server 2017: mainstream support ended 11 October 2022. Extended support ends 12 October 2027.
- SQL Server 2019: mainstream support ended 28 February 2025. Extended support ends 8 January 2030.
- SQL Server 2022: mainstream support ends 11 January 2028. Extended support ends 11 January 2033.
- SQL Server 2025: released 18 November 2025. Mainstream support ends 6 January 2031. Extended support ends 6 January 2036.
Microsoft publishes these on its product lifecycle pages as timestamps in Pacific time, so you will sometimes see the day before or after quoted. The month is what matters for planning.
What mainstream versus extended support actually changes
Both 2017 and 2019 are already out of mainstream support. That means no more cumulative updates: the bug you hit next month will not be fixed in your version, and Microsoft support for a non-security problem will point you at an upgrade. Security updates continue until the extended date, which is why many estates treat extended support as good enough. It is, until it is not: an application vendor drops certification for the version, an auditor asks about the patch position, or a feature you need exists only in a newer release. The extended support date is the deadline. The mainstream date was the warning.
The risks of running past the date
- Unpatched vulnerabilities. A database engine holding personal and financial data with no security updates is exactly the exposure that POPIA's security safeguards and most cyber-insurance questionnaires ask about.
- Vendor support. Microsoft will not support it, and application vendors follow Microsoft. The first serious incident becomes a negotiation about whose problem it is.
- The operating system underneath. Windows Server versions reach their own end of support around the same time as the SQL Server they host. Check both in the same review; an upgrade that fixes one and not the other has not fixed the risk.
- Compatibility drift. Newer drivers, backup tools, monitoring agents and cloud services stop testing against old versions quietly.
- Compressed timelines. The estates that end up in trouble are the ones that started planning in the last quarter before the date. A version upgrade across a production estate is a project measured in months, not weeks.
A useful test: for each instance, write down the SQL Server version, the Windows version, the application that depends on it and the vendor's certified versions. Any row with two dates inside the next eighteen months is your priority list.
Your options, ranked
- Upgrade in place to SQL Server 2022 or 2025. Same hosting, same licence model, longest runway on 2025. The right default for stable estates on hardware with life left. The work is compatibility testing and a rehearsed upgrade, not a redesign.
- Upgrade and consolidate. If you have several old instances, use the upgrade to consolidate onto fewer, better-specified servers or a single newer instance. Fewer things to patch, back up and pay for.
- Move to Azure and upgrade at the same time. Azure SQL Managed Instance takes the version question away permanently; SQL Server on an Azure virtual machine keeps full control on a current version. Only merge the two decisions if the cloud move already has its own business case. Our guide to migrating SQL Server to Azure sets out the steps.
- Extended Security Updates as a bridge. Microsoft has offered paid security updates for versions past extended support, and has bundled them with Azure hosting for some versions. Confirm the current terms for your version. This buys time; it does not remove the work.
- Do nothing. Legitimate only for an isolated, non-production or soon-to-be-retired instance, with the decision written down and the retirement date real.
How an upgrade actually goes
Inventory every instance and database with version, edition, compatibility level and dependent applications. Run the compatibility assessment against the target version and fix what it finds on the current platform. Build the target, restore a copy of production, run the real application and compare query performance against a baseline, because plans change between versions and a handful of queries always need attention. Restore-test the new environment before cutover, not after. Then a rehearsed cutover with a rollback path, keeping the old instance intact until the new one has been through a month-end.
How RadixTrie helps
RadixTrie is a South African database specialist with senior engineers across Microsoft SQL Server, Oracle and PostgreSQL, with offices in Randpark Ridge and Stellenbosch. We assess estates against these dates, rank the options for each instance and run the upgrades and migrations, and then keep the estate patched and supported afterwards under managed DBA services. The model is direct access to senior database experts, with no service desk and no escalation loops. Our SQL Server support services page describes the cover, and if you are still on 2016, our note on SQL Server 2016 leaving extended support ranks the options for that version specifically.
TAGSSQL ServerEnd of SupportUpgradeMigrationSouth Africa