Microsoft lifecycle

SQL Server extended support has ended or is ending. What happens next?

When Microsoft SQL Server extended support ends, regular security updates stop. Extended Security Updates are available as a bridge, but ESU is purchased on top of your current licensing and is not a long-term plan.

After the end-of-support date, an unpatched production instance becomes an audit finding, an insurance question, and an executive risk that somebody has to sign.

What extended support ending means

• No more regular security patches from Microsoft
• New CVEs will not be fixed on an out-of-support release
• Compliance frameworks (SOC 2, ISO, PCI-DSS, HIPAA) expect supported software
• Auditors and insurance underwriters will ask when you plan to upgrade
• ESU is an annual purchase — a stopgap, not an indefinite answer

The real cutover risk

The reason companies delay upgrades is not the SQL Server engine — it is the applications, jobs, SSIS packages, linked servers, collations, and compatibility assumptions that sit on top. Production is not a lab. A failed upgrade on a weekend becomes an outage.

We rebuild your environment in isolation, run the upgrade there, prove it works, then we can execute production go-live or your team can run the verified scripts and runbook. Jobs, linked servers, cutover sequence — handled in the replica first.

Microsoft lifecycle dates

These dates are from the Microsoft Lifecycle policy. SQL Server 2012, 2014, and 2016 extended support have already ended. SQL Server 2017 ends in October 2027.

Your upgrade path

A typical upgrade lands on:

• SQL Server 2022 or 2025, on-prem or on an Azure, AWS, or Google VM
• Azure SQL Database or Azure SQL Managed Instance
• Amazon RDS for SQL Server when that is the target you already chose

If your plan is to move the workload to another engine (PostgreSQL, Amazon Aurora, Google Cloud SQL), that is a workload migration, not only an upgrade. If you are landing data onto a warehouse platform, that is SQL Server to a data platform.

What an assessment covers

The assessment request is how we start. We reply with a recommended path (upgrade, migrate, or data platform), what we would need next (inventory, transfer channel), and whether the work is a fit. There is no price list — delivery is scoped in a written SOW.

Request an assessment

Version-specific guidance

For lifecycle dates and upgrade paths by version:

• SQL Server 2012 end of support — ended 12 July 2022
• SQL Server 2014 end of support — ended 9 July 2024
• SQL Server 2016 end of support — ended 14 July 2026
• SQL Server 2017 end of support — ends 12 October 2027
• SQL Server 2019 end of support — ends 8 January 2030