Logo-Icon
HOMEABOUTSERVICESHOW WE WORKBLOGInstagram-Icon Talk To an Expert
RadixTrie-image
SQL Server 2017 and 2019 end of support dates and options
Architecture

SQL Server 2019 End of Life: 8 January 2030 (and 2017: 12 October 2027)

SQL Server 2019 reaches end of life on 8 January 2030, when Microsoft's extended support ends; SQL Server 2017 follows on 12 October 2027. What each date means, why no ESU programme exists for either, the dates for SQL Server 2022 and 2025, and the options ranked for any estate, wherever it runs.
Planning your SQL Server upgrade? Talk to a senior SQL Server DBA ↓
By RadixTrie14 September 20268 min read
Updated 16 October 2026. SQL Server 2019 reaches end of life on 8 January 2030, when Microsoft's extended support ends. Mainstream support ended on 28 February 2025, so the version now receives security fixes only. Running SQL Server 2017 as well? Its date is 12 October 2027 and it has its own page: SQL Server 2017 end of life (12 October 2027).
No Extended Security Updates programme has been announced for SQL Server 2019 (or for 2017): Microsoft's ESU page lists SQL Server 2014 and 2016 only. The supported targets today are SQL Server 2022, with extended support to 11 January 2033, and SQL Server 2025, to 6 January 2036. Both accept a direct in-place upgrade from 2019.
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, and the day it ends is what most people mean by end of life. After extended support ends, nothing ships unless Microsoft sells Extended Security Updates for that version, and for 2019 it has announced none. SQL Server 2016 crossed that last line in July 2026. This article is about SQL Server 2019, the version most estates run, with the SQL Server 2017 dates alongside for estates that run both.

SQL Server 2019 dates

Released: 4 November 2019
Mainstream support ended: 28 February 2025
Extended support ends (end of life): 8 January 2030
Big Data Clusters: retired 28 February 2025
Extended Security Updates: none announced; Microsoft offers ESUs for SQL Server 2014 and 2016 only, as at 16 October 2026
Platforms covered: the same dates apply on Windows and on Linux, all editions
SQL Server 2017, for estates that run both: mainstream support ended 11 October 2022; extended support ends 12 October 2027; no ESU announced
Microsoft's lifecycle page shows the cut-offs as timestamps in Pacific time (3/1/2025 6:59:59 AM and 1/9/2030 6:59:59 AM), which is why some pages quote the day after. Microsoft's own documents quote the day before the timestamp, and this article follows Microsoft.

Where to move

SQL Server 2025: released 18 November 2025; mainstream support ends 6 January 2031; extended support ends 6 January 2036; direct in-place upgrade from 2019: yes
SQL Server 2022: released 16 November 2022; mainstream support ends 11 January 2028; extended support ends 11 January 2033; direct in-place upgrade from 2019: yes
Azure SQL Managed Instance: no version and no end-of-support date (Microsoft describes it as a fully managed service that never reaches end of support); a migration rather than an upgrade
Dates from Microsoft's lifecycle pages for SQL Server 2022 and SQL Server 2025. Upgrade paths from Microsoft's supported version and edition upgrades for SQL Server 2025, which lists SQL Server 2019 (15.x) and SQL Server 2017 (14.x) as supported sources. One edition detail: Web edition does not exist in SQL Server 2025, so a Web edition instance upgrades to Standard or Enterprise.

What mainstream versus extended support actually changes

SQL Server 2019 left mainstream support on 28 February 2025, and 2017 on 11 October 2022. In Microsoft's words, mainstream support 'includes functional, performance, scalability, and security updates' and extended support 'includes only security updates'. That means no more cumulative updates: the bug you hit next month will not be fixed in your version, and a support case 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. Microsoft's end of support options page sets out the stages and the routes out.

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 2016 reaches end of support on 12 January 2027, long before SQL Server 2019 does. SQL Server 2019 is supported on Windows Server 2025, so the operating system can be refreshed first; check both dates in the same review, because 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. For SQL Server 2017 that last quarter is mid-2027.
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

  1. Upgrade in place to SQL Server 2025 or 2022. Same hosting, same licence model, longest runway on 2025. The right default for stable estates on hardware with life left. Microsoft supports the in-place upgrade from both 2019 and 2017. The work is compatibility testing and a rehearsed upgrade, not a redesign.
  2. 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.
  3. 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.
  4. Extended Security Updates as a bridge: not available. Microsoft has sold ESUs for up to three years after extended support for 2014 and 2016 (about 75% of the licence cost a year, by Microsoft's own description) and has announced nothing for 2019 or 2017. Plan without it.
  5. 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. Databases keep their compatibility level through the upgrade (Microsoft's upgrade page confirms a level of 100 or higher is unchanged), so an application only needs full recertification when you raise the level. 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.

SQL Server 2019 end of life: common questions

When is SQL Server 2019 end of life?

8 January 2030, when extended support ends. Microsoft's lifecycle page for SQL Server 2019 shows the cut-off as 1/9/2030 6:59:59 AM Pacific time; Microsoft's own documents quote the day before such timestamps. Mainstream support ended on 28 February 2025, the same day Big Data Clusters were retired.

Is SQL Server 2019 still supported in 2026?

Yes, for security updates only. SQL Server 2019 has been in extended support since 28 February 2025: no cumulative updates since then and no fixes for non-security bugs, but security fixes until 8 January 2030. Microsoft's end of support options page defines the two stages.

Will SQL Server 2019 stop working on 8 January 2030?

No. The instance starts, queries run and backups complete. What stops is the supply of security fixes and Microsoft support. The practical deadline is usually earlier and is set by other people: the application vendor's certification matrix, the cyber-insurer's questionnaire and the auditor's patch-status question. Treat 8 January 2030 as the last possible date, not the target.

Is there an ESU programme for SQL Server 2019?

Not as at 16 October 2026. Microsoft's Extended Security Updates page says ESUs 'are available for SQL Server 2014 (12.x), and SQL Server 2016 (13.x)'. For those versions ESUs cover Critical security updates for a maximum of three years after extended support ends, at 'approximately 75% of the on-premises license cost annually' in Microsoft's description, through Software Assurance or Azure Arc. Nothing equivalent has been announced for 2019 or 2017.

Can we upgrade SQL Server 2019 straight to SQL Server 2025?

Yes. Microsoft's supported version and edition upgrades page for SQL Server 2025 lists SQL Server 2019 (15.x) as a supported source for an in-place upgrade, as it does 2017 (14.x), 2016 SP3, 2014 SP3 and 2022. Databases at compatibility level 100 or higher keep their level through the upgrade, so engine behaviour changes only when you raise it.

Does SQL Server 2019 run on Windows Server 2025?

Yes. Microsoft's requirements page for SQL Server 2019 (updated 20 July 2026) lists Windows Server 2025 Datacenter, Datacenter: Azure Edition, Standard and Essentials for every edition, and Windows Server 2025 Core for Server Core installations. SQL Server 2017 is a different story: Microsoft lists it up to Windows Server 2022 only.

Should we choose SQL Server 2022 or 2025?

SQL Server 2025 for the longest runway: mainstream support to 6 January 2031 and extended support to 6 January 2036. SQL Server 2022 (11 January 2028 and 11 January 2033) when an application vendor certifies 2022 and not yet 2025. Both accept the direct upgrade from 2019 and from 2017, so the choice is about vendor certification and runway, not effort.

How RadixTrie helps

RadixTrie is a database specialist with senior engineers across Microsoft SQL Server, Oracle and PostgreSQL, based in South Africa and working with organisations in the US, UK, Europe and beyond through our remote DBA services. 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 DBA services page describes the cover (for estates in South Africa, see SQL Server support services), a database health check is the usual first step, and every one of our database services is delivered by the engineer who does the work. Still on 2016? Our note on SQL Server 2016 leaving extended support ranks the options for that version specifically.
Not sure which of your instances hits a date first? Let's build the list together.

Planning your SQL Server upgrade?

Tell us what you run today and when it has to move. A senior SQL Server DBA will reply directly, usually within one working day. Prefer email or phone? Write to expert@radixtrie.com or call +27 10 143 0304.

By submitting this form you agree to our Privacy Policy and consent to being contacted about your enquiry. Conversations stay confidential and focused on your environment.

TAGSSQL ServerEnd of SupportUpgradeMigrationSouth AfricaEnd of Life