SQL Server End of Support Dates by Version
SQL Server end of support dates: 36 versions are listed below. 32 are already past Microsoft's end of support, most recently SQL Server 2016 SP3 on Jul 14, 2026; the next to end is SQL Server 2017 'Helsinki' on Oct 12, 2027. Microsoft sells Microsoft Extended Security Updates (ESU) for a limited period after that date. Third-party support keeps any of these versions in production after the vendor date, with 24x7 incident response, vulnerability mitigation and compliance documentation, typically at 40-70% below the vendor's renewal.
SQL Server versions and end of support dates
"Vendor end of support" is the date Microsoft stops free fixes and security updates. "Extended end" is the end of the paid extension where Microsoft offers one. Each version links to its own page and quote form.
Why SQL Server versions stay in production
SQL Server versions persist because the application vendor certified a specific version, or because the database is simply working. SQL Server 2012, 2014 and 2016 estates are still common for both reasons.
Microsoft sells ESU per core for three years after Extended Support ends. Third-party support is the alternative when the plan is to keep the instance running or to migrate on your own schedule.
How Microsoft's support lifecycle works for SQL Server
Microsoft publishes a Fixed Lifecycle policy for on-premises server and desktop products: five years of Mainstream Support, five years of Extended Support, and for some products paid Extended Security Updates (ESU) for up to three further years. Mainstream end stops feature updates and non-security fixes; Extended end stops free security updates.
ESU is per-device or per-core, priced to rise each year, and buys security patches only. It is usually the comparison point for third-party support on an estate you intend to keep running.
What changes on the end of support date
- Microsoft stops free security updates and cumulative updates for the version.
- ESU becomes the only source of security patches, priced per core.
- Instances, Always On groups, replication and SSIS packages keep running.
Your options after SQL Server end of support
1. Upgrade to a supported version
Right when the application above it is ready and the budget exists. Wrong as a forced move: an upgrade driven by a support date rather than a business need is where regression bugs and surprise licence costs come from.
2. Buy Microsoft Extended Security Updates (ESU)
Microsoft's paid extension buys more time at a price that rises each year and typically covers security fixes only. It keeps the deadline in place and is often the most expensive line in the renewal.
3. Third-party support
Replaces the vendor contract with ours for the versions you run, with no deadline. For SQL Server that covers:
- Database engine, Always On, replication, SSIS, SSRS and SSAS incidents, 24x7
- Performance tuning, corruption and recovery assistance on the version you run
- Hardening and compensating controls for unpatched vulnerabilities
- Migration planning to a current SQL Server, Azure SQL or PostgreSQL when you are ready
Not included: new vendor patches or licences. Those stay with Microsoft; everything operational moves to us.
SQL Server end of support: frequently asked questions
Which SQL Server versions are out of support?
SQL Server 2016 SP3 (Jul 14, 2026), SQL Server 2016 SP3 Azure Connect Pack (Jul 14, 2026), SQL Server 2014 'Hekaton' SP3 (Jul 9, 2024), SQL Server 2012 'Denali' SP4 (Jul 12, 2022), SQL Server 2016 SP2 (Oct 11, 2022), SQL Server 2008 'Katmai' SP4 (Jul 9, 2019), SQL Server 2008 R2 'Kilimanjaro' SP3 (Jul 9, 2019), SQL Server 2014 'Hekaton' SP2 (Jan 14, 2020) and 24 earlier versions. All of them can be covered by third-party support.
Can SQL Server 2014 or 2016 stay supported after Microsoft end of support?
Yes. Third-party support covers the engine and its services with 24x7 incident response and vulnerability mitigation. ESU remains the only source of Microsoft patches.
Does third-party support include SQL Server licensing?
No. Your existing licences continue; we support the software you own.
What does third-party support for SQL Server cost?
Typically 40 to 70% below the vendor renewal or extended-support price for the same versions, priced per instance, server or core depending on the product. We return an indicative price within 24 hours and a firm quote within 48.
How do we move SQL Server to third-party support without a gap?
Start before the vendor renewal date: inventory versions and instances, download all media and fixes you are entitled to, confirm no bundled contract depends on the renewal, then let the vendor support lapse as ours starts. We handle the hand-over checklist with you.
Version-by-version guides
- Microsoft SQL Server 2017 EOL: Budget for October 2027 (Sep 12, 2026)
- SQL Server 2016 SP3 Azure Connect Pack EOL: July 14, 2026 (Jul 14, 2026)
- SQL Server 2016 SP3 End of Life July 14, 2026 (Jul 14, 2026)
- SQL Server 2016 SP3 Azure Connect Pack EOL July 14, 2026 (Apr 14, 2026)
- SQL Server 2016 SP3 End-of-Life Action Plan (60 chars) (Apr 14, 2026)
- SQL Server 2016 SP3 EOL July 14, 2026: Six Months to Decide (Jan 14, 2026)
- SQL Server 2016 SP3 EOL July 2026 – Act Now (Jan 14, 2026)
- SQL Server 2016 SP3 EOL: 3 Options Before July 2026 (Oct 14, 2025)