On this page · 12 sections
- What stops on 12 October 2027
- The 2026 picture: no 2017 ESU offer, and Azure is no longer free
- How SQL Server ESUs are licensed and priced today
- Upgrade paths from SQL Server 2017
- Compatibility levels: upgrade the engine first, the database later
- Assessment tooling now that DMA is retired
- Which path for which SQL Server 2017 instance
- Worked example: an ESU bridge versus upgrading
- A 2027 timeline that works back from 12 October
- India, EU and US notes
- How eCorpIT can help
- References
Summary. Extended support for SQL Server 2017 ends on 12 October 2027 for every edition on Windows and Linux; after that Microsoft releases no security fixes and takes no support cases. As of 7 November 2026, Microsoft offers Extended Security Updates (ESUs) only for SQL Server 2014 and 2016 and has announced nothing for 2017. Two 2026 changes shape any future offer: free ESUs on Azure VMs stopped with SQL Server 2016, and ESU offers released from 1 April 2026 carry the same list price in Azure, on-premises and other clouds. The current benchmark, SQL Server 2016 ESUs, lists at $0.19 per core-hour for Standard and $0.74 for Enterprise, about $138.70 and $540.20 per core a month, with a four-core minimum. That is more than SQL Server 2025 pay-as-you-go licensing at $73 and $274 per core a month. SQL Server 2025 accepts an in-place upgrade from every 2017 edition but needs Windows Server 2019 or later, so instances on Windows Server 2016 (unsupported from 12 January 2027) need a new host first. Upgrade or migrate; treat ESUs as a contingency that may never exist.
About this article. For IT managers, database administrators and budget owners still running SQL Server 2017. We checked every date, price and support statement on 7 November 2026 against Microsoft's lifecycle pages, Microsoft Learn, Microsoft's licensing news and pricing datasheet, and the Azure Retail Prices API. Prices are US list prices before tax and discounts and change often. This is not licensing or legal advice, and no vendor paid for inclusion. Researched with AI assistance and reviewed by our editorial team.
This is the deadline and execution guide. For where the databases should land, see our comparison of SQL Server 2025, Azure SQL Managed Instance and PostgreSQL. Many SQL Server 2017 instances sit on Windows Server 2016, and our Windows Server 2016 migration playbook covers the operating system side.
What stops on 12 October 2027
Microsoft's lifecycle page lists SQL Server 2017 under the Fixed Lifecycle Policy, on Linux and Windows, all editions. It timestamps the end of extended support as 13 October 2027, 06:59:59 Pacific Time, and Microsoft's 2027 end-of-support list gives the date as 12 October 2027. From then there are no security or non-security updates, no assisted support and no online content updates. Mainstream support ended in October 2022, and Microsoft never released service packs for 2017, so cumulative updates are the only servicing baseline.
Several nearby dates matter for the same servers, per Microsoft's lifecycle and Linux support pages and Red Hat's life cycle page.
| Date | Event | Why it matters for a 2017 estate |
|---|---|---|
| 12 Jan 2027 | Windows Server 2016 extended support ends | A common host OS for SQL Server 2017 goes first |
| 12 Jul 2027 | SQL Server 2014 ESU Year 3 ends | Older instances on the same hosts lose their last patches |
| 12 Oct 2027 | SQL Server 2017 extended support ends | No fixes for the engine or the 2017 versions of SSRS, SSIS and SSAS |
| 17 Jul 2029 | SQL Server 2016 ESUs end | Upper limit for any 2016 stragglers |
| Already passed | RHEL 7 (June 2024), SLES 12 (October 2024) and Ubuntu 18.04 (April 2023) left standard support | Three of the four Linux releases SQL Server 2017 supports are past standard support; RHEL 8 is the exception |
From 7 November 2026, 339 days remain. Windows Server 2016 ends in 66 days, so many teams must fix the host first.
The 2026 picture: no 2017 ESU offer, and Azure is no longer free
Microsoft's SQL Server ESU overview and ESU FAQ (last updated 19 October 2026) cover SQL Server 2014 and 2016 only, and its end-of-support planning page lists no 2017 date. Earlier offers ran for up to three years after extended support ended; that is a pattern, not an announcement. Plan as if no 2017 ESUs will exist.
Three 2026 facts cut against the old advice to move servers to Azure for free patches:
- Free Azure ESUs ended with SQL Server 2016. From SQL Server 2016, moving to SQL Server on Azure VMs no longer gives free ESUs. Only SQL Server 2014 keeps free ESUs on Azure VMs, Azure VMware Solution and Azure Stack.
- A pricing rule now covers every new ESU offer. On 27 March 2026 Microsoft announced that Windows and SQL Server ESUs released on or after 1 April 2026 carry the same list price whether you deploy in Azure, on-premises or another public cloud, and whatever the purchasing channel.
- The price list reflects it. The Azure Retail Prices API lists meters named Azure ESU 2016 at the same $0.19 (Standard) and $0.74 (Enterprise) per hour as the Arc ESU 2016 meters, effective 1 June and 1 April 2026 respectively.
Our Windows Server 2016 vs 2025 vs Azure Local comparison shows the same rule applied to Windows Server 2016 ESUs.
How SQL Server ESUs are licensed and priced today
Until Microsoft publishes 2017 terms, the SQL Server 2016 programme is the best guide.
| Term | SQL Server 2016 ESUs (current benchmark) |
|---|---|
| Coverage | Security updates rated Critical by MSRC, released only when needed, for up to 3 years |
| Editions | Enterprise and Standard only; not Express, Web or Developer |
| Eligibility | Active Software Assurance (EA, EAS, SCE or EES), a SQL Server subscription, or pay-as-you-go licensing through Azure |
| Standard price | $0.19 per core-hour, about $138.70 per core per month |
| Enterprise price | $0.74 per core-hour, about $540.20 per core per month |
| Minimum | 4 cores per VM or physical OS environment |
| Standard cap | Billed for up to 24 cores, even on larger machines |
| Unlimited virtualisation | Physical-core ESU licence on the Enterprise meter, 16-core minimum per licence |
| Late sign-up | Bill-back to the start of the current ESU year |
| Free cover | Developer edition, Azure dev/test subscriptions and qualifying passive HA/DR replicas, once production is subscribed |
| Price in Azure | Same list price as on-premises |
Monthly figures use Azure's 730-hour month ($0.19 x 730 and $0.74 x 730). Microsoft's own end-of-support guide puts ESUs at roughly 75% of the on-premises licence cost per year.
There are five ways to buy ESUs.
| Route | How it bills | Best for |
|---|---|---|
| Azure Arc, virtual cores | Hourly per VM, Standard or Enterprise meter | VMs mixed with other workloads, or at hosters and other clouds |
| Azure Arc, physical cores without VMs | Hourly on all physical cores of the host | SQL Server installed directly on hardware |
| Azure Arc, physical cores with unlimited virtualisation | Hourly on the Enterprise meter per licensed host | Many out-of-support VMs on designated hosts |
| SQL Server on Azure VMs | Hourly through the SQL IaaS Agent extension | Instances already rehosted to Azure |
| Volume Licensing | Through your Microsoft account team, then register the disconnected instance | Servers that cannot connect to Azure Arc |
Three rules catch teams out. Server+CAL licences do not qualify. The workaround is pay-as-you-go licensing, which adds a licence meter on top of the ESU meter. ESUs build on the latest cumulative update, so servers patched only with GDR updates should install and validate the latest CU when they subscribe. Identity changes can double-bill. If a machine's VM ID changes after a rebuild, migration, hardware change or clone, Arc treats it as a new machine and bills back again unless you unsubscribe the old resource first.
Upgrade paths from SQL Server 2017
SQL Server 2019, 2022 and 2025 all accept SQL Server 2017 as a direct upgrade source, so lifecycle dates decide.
| Target | Mainstream support | Extended support | In-place from 2017 | Verdict |
|---|---|---|---|---|
| SQL Server 2019 | Ended February 2025 | January 2030 | Yes | Security fixes only; short runway |
| SQL Server 2022 | To January 2028 | January 2033 | Yes | Acceptable if an ISV certifies nothing newer |
| SQL Server 2025 | To January 2031 | January 2036 | Yes | Default target |
Microsoft's upgrade matrix for SQL Server 2025, updated on 6 November 2026, lists SQL Server 2017 as a supported source with no service pack requirement. Enterprise upgrades to Enterprise; Standard to Standard or Enterprise; Express to Express, Standard or Enterprise. Web edition no longer exists in SQL Server 2025, so 2017 Web instances move to Standard or Enterprise. Developer installs move to the new Enterprise Developer edition, or to a paid edition.
The operating system decides how you get there:
- Windows. SQL Server 2025 requires Windows Server 2019 or later, or Windows 10 or 11 for Standard and Express; Enterprise is not supported on client Windows. A SQL Server 2017 instance on Windows Server 2016 cannot upgrade in place until the OS does. A new Windows Server 2025 VM with a restore or log-shipping cutover is usually cleaner.
- Linux. SQL Server 2017 ran on RHEL 7.7 to 7.9 or 8.x, SLES 12 SP3 to SP5 and Ubuntu 18.04. SQL Server 2025 supports RHEL 9.x and 10.x and Ubuntu 22.04 and 24.04, and drops SLES entirely. None of the 2017 distributions is on the 2025 list, so Linux instances need a new or upgraded host. Prefer Ubuntu 24.04 or RHEL 9 or 10: Ubuntu 22.04 leaves standard support in May 2027, before the SQL Server deadline (see our Ubuntu 22.04 end of standard support guide).
Setup is blocked by a pending restart or a stopped Windows Installer service, and you cannot add features during the upgrade. Two product changes also need a plan:
- Reporting Services. From SQL Server 2025, on-premises reporting is consolidated under Power BI Report Server. SSRS 2017 report servers need a migration plan of their own.
- Edition limits. SQL Server 2025 Standard uses up to 32 cores and 256 GB of buffer pool memory per instance, against 24 cores in 2022 and earlier, and Express allows 50 GB databases. Some estates that bought Enterprise only for scale can drop back to Standard.
Compatibility levels: upgrade the engine first, the database later
An engine upgrade does not by itself change how your queries behave. Databases keep their compatibility level when you upgrade, restore or attach them, as long as it is 100 or higher.
| Platform | Default level | Supported levels |
|---|---|---|
| SQL Server 2017 | 140 | 140, 130, 120, 110, 100 |
| SQL Server 2022 | 160 | 160 down to 100 |
| SQL Server 2025 | 170 | 170 down to 100 |
| Azure SQL Managed Instance (SQL Server 2025 or Always-up-to-date policy) | 170 | 170 down to 100 |
Microsoft documents that cardinality estimator changes, and query optimiser fixes shipped earlier behind trace flag 4199, are enabled only at the default level of each new engine. That allows a two-step method: move the engine while databases stay at 140, capture a Query Store baseline under real load, then raise the level and use Query Tuning Assistant, built into SSMS since version 18, to catch regressions.
-- 1. After the engine upgrade, confirm levels and turn on Query Store
SELECT name, compatibility_level FROM sys.databases;
ALTER DATABASE [Sales] SET QUERY_STORE = ON;
-- 2. After a representative baseline period, move to the new default
ALTER DATABASE [Sales] SET COMPATIBILITY_LEVEL = 170;
Keep step 2 off the cutover weekend: a level change reverts in seconds, while an engine rollback means rebuilding on 2017 and restoring old backups.
Assessment tooling now that DMA is retired
Microsoft retired the Data Migration Assistant (DMA) on 16 July 2025, so older runbooks that start with DMA need updating. The current tools:
| Tool | Use it for | Notes |
|---|---|---|
| SSMS migration component (SSMS 21 or later, Hybrid and Migration workload) | Upgrade assessment to a newer SQL Server: breaking changes, behaviour changes, deprecated features; feature parity checks for cross-platform moves | Also migrates databases and logins by backup and restore; no Azure SQL targets; no TDE databases |
| Azure Migrate | Discovery through the Azure Migrate appliance and Azure SQL assessments | Configuration-based or performance-based sizing and monthly cost estimates |
| SQL Server enabled by Azure Arc | Inventory, ESU subscriptions and Microsoft's Arc migration route to Managed Instance | The same agent you would need for ESUs |
| Azure Database Migration Service | Moving databases into Azure SQL targets | Online or offline to Managed Instance and SQL Server on Azure VMs; offline to Azure SQL Database; no assessment of its own |
| Managed Instance link | Near-real-time replication from SQL Server 2017 to Managed Instance for a low-downtime cutover | Needs SQL Server 2017 CU31 (14.0.3456.2) and the matching Azure Connect pack (14.0.3490.10); one way only |
| Query Tuning Assistant | Raising the compatibility level after an upgrade | Built into SSMS |
Start with Arc and Azure Migrate for the estate view, then run SSMS assessments per database.
Which path for which SQL Server 2017 instance
| Instance type | Recommended path | Why |
|---|---|---|
| Windows Server 2019 or later, ISV supports 2025 | In-place upgrade to SQL Server 2025 | Fastest; keeps logins, jobs and settings |
| Running on Windows Server 2016 | New Windows Server 2025 VM with SQL Server 2025, then restore or log-ship | Avoids two in-place upgrades and clears both deadlines at once |
| SQL Server 2017 on Linux | New RHEL 9 or 10 or Ubuntu 24.04 host with SQL Server 2025 | No 2017-era distribution is supported by 2025 |
| Hardware or data centre lease ending | Managed Instance through the MI link, or SQL Server 2025 on an Azure VM | Removes the hardware refresh |
| ISV certified only on 2017 | Push the vendor now; budget for ESUs only if Microsoft announces them | No 2017 ESU offer exists today |
| Heavy SSRS use | Upgrade the engine, migrate reports to Power BI Report Server | SSRS is consolidated from 2025 |
Worked example: an ESU bridge versus upgrading
An illustrative estate, not a client case: six application VMs run SQL Server 2017 Standard with 4 vCores each (24 cores), and one physical server runs SQL Server 2017 Enterprise on 16 cores. SQL Server 2017 ESU prices are not published, so we use the 2016 meters as a planning proxy only. SQL Server 2025 list prices from Microsoft's datasheet: $3,945 (Standard) and $15,123 (Enterprise) per 2-core pack, subscriptions at $1,418 and $5,434 per 2-core pack a year, and Arc pay-as-you-go at $73 and $274 per core a month.
| Option | Arithmetic | 12-month cost |
|---|---|---|
| ESU proxy, Standard VMs | 24 cores x $138.70 x 12 | $39,945.60 |
| ESU proxy, Enterprise host | 16 cores x $540.20 x 12 | $103,718.40 |
| ESU proxy, total | On top of existing licences and SA | $143,664 |
| SQL Server 2025, Arc pay-as-you-go | 24 x $73 x 12 + 16 x $274 x 12 | $73,632 |
| SQL Server 2025, subscription | 24 x $709 + 16 x $2,717 | $60,488 |
| SQL Server 2025, perpetual licences | 24 x $1,972.50 + 16 x $7,561.50 | $168,324 one-off, SA extra |
How to read it:
- A year of ESUs at 2016 rates costs about twice a year of SQL Server 2025 pay-as-you-go ($143,664 against $73,632), for Critical security fixes only.
- ESUs approach the price of new licences. Twelve months of the proxy is about 85% of perpetual SQL Server 2025 licences for the same cores ($143,664 divided by $168,324).
- Software Assurance changes the maths. With SA new-version rights, the upgrade may add no licence cost; confirm it in your agreement.
- Re-test Enterprise needs. With Standard now allowing 32 cores and 256 GB, check whether the Enterprise host still needs Enterprise-only features.
A 2027 timeline that works back from 12 October
| Window | Actions | Exit criterion |
|---|---|---|
| Nov 2026 to Jan 2027 | Connect every instance to Azure Arc; record version, edition, CU, host OS, ISV and owner. Fold 2017 instances on Windows Server 2016 into the OS plan. | Complete inventory with owners |
| Feb to Mar 2027 | Run Azure Migrate and SSMS assessments. Request ISV statements for SQL Server 2025. Pick a target per instance. | Path and date per instance |
| Apr to May 2027 | Pilot three to five databases. Rehearse restore, log shipping or MI link cutovers. Test SSRS migration. | Pilot signed off |
| Jun to Aug 2027 | Waves, highest risk first, keeping compatibility level 140 at cutover. | Waves on schedule |
| Sep 2027 | Finish stragglers. If a 2017 ESU offer exists, enrol before 12 October; a later start is billed back to the first day of the ESU year anyway. | Every instance upgraded, migrated or covered |
| Oct 2027 onward | Raise compatibility levels one database at a time. | All databases on the new default |
India, EU and US notes
India. The Azure Retail Prices API lists Azure SQL Managed Instance prices for Central India, South India, West India and India South Central, plus two Jio regions, and prices differ by region. For the 2016 ESU benchmark, Central India is the only Indian region on Microsoft's list for ESUs on SQL Server Azure VMs. If databases move to Azure, keep personal data in Indian regions where your sector regulator expects it.
EU. If the exit includes a move to cloud, read our note on the EU Data Act cloud switching rules before you sign multi-year commitments.
US. Microsoft's FAQ says Azure Arc is not supported for SQL Server 2016 ESUs in Azure Government regions, so government customers buy them through volume licensing and register disconnected instances, or move to SQL Server on Azure VMs in Azure Government.
How eCorpIT can help
eCorpIT is a Gurugram-based technology organisation, founded in 2021, assessed at CMMI Level 5 and MSME certified, with senior-led engineering teams working across AWS, Microsoft and Google platforms. Our data and analytics services team runs SQL Server 2017 exits, from Arc inventory to cutover and compatibility testing. Talk to us at /contact-us/.
Last updated: 7 November 2026.
