The Life of SQL Server: Knowing Where Your Environment Stands
SQL Server 2016 reached end of life earlier this year. SQL Server 2017 follows in late 2027. For consultants who track this closely, neither date is a surprise—Microsoft has run an organized, predictable lifecycle for nearly every version it has shipped. For the business leaders who depend on these systems, though, an EOL date can arrive as an unwelcome surprise. Here is how the lifecycle works, and how to plan around it.
Core Lifecycle Phases
Microsoft supports each version of SQL Server for a maximum of ten years, split into three phases. Phase 1, Mainstream Support, covers years one through five and is the only fully active phase—it begins immediately at General Availability. Phase 2, Extended Support, covers years six through ten and is far less active. Phase 3, Extended Security Updates, is an optional three-year extension available only after a version has reached end of life, and it provides the narrowest level of support.
Phase 1 – Mainstream Support (Years 1–5)
This is Microsoft's active phase of the lifecycle, beginning immediately at General Availability. It includes feature updates, performance improvements, design changes, bug fixes, and security updates—all covered under standard licensing and Software Assurance.
Phase 2 – Extended Support (Years 6–10)
Once Mainstream Support ends, Extended Support takes over. This phase provides only security updates and critical bug fixes—no new features, functional improvements, or design changes. Staying covered here requires keeping current on Service Packs or Cumulative Updates, still under standard licensing and Software Assurance.
Phase 3 – Extended Security Updates (Optional, Up to 3 Years)
SQL Server reaches end of life at the end of year ten. Migrating to a newer version is the recommended path forward. When that is not yet possible, Microsoft offers Extended Security Updates as a last resort for up to three years, covering critical security patches only. ESU requires an additional annual subscription, unless the workload is migrated to Azure VMs, where it is available at no extra cost.
Recommended Lifecycle Strategy
We advise clients to treat the lifecycle as a planning calendar, not a deadline to react to. The table below maps each window to the action it calls for.
| Cycle | Roadmap |
|---|---|
| Years 1–3 (Mainstream) |
Optimal Baseline — the ideal window to deploy new builds or upgrade existing environments. The version is stable, well-patched, and actively supported with ongoing performance improvements. |
| Years 4–5 (Late Mainstream) |
Evaluating & Planning — if running an older version, start evaluating the next major release. Begin testing application-workload compatibility with tools like the Data Migration Assistant (DMA). |
| Years 6–10 (Extended Support) |
Active Migration — production environments should be migrated to a newer version shortly before or after Extended Support begins. |
| Post-Year 10 (ESU) | Critical Risk — operating past year ten exposes the environment to unpatched vulnerabilities and regulatory compliance failures. |
Microsoft SQL Server Versions as of 2026
For reference, here is where every released version of SQL Server currently sits against that timeline.
| Version | Initial Release | Mainstream Support End | Extended Support (EOL) | Status |
|---|---|---|---|---|
| SQL Server 1.0 | April, 1989 | — | — | Ended |
| SQL Server 4.2/4.21 | 1992 | — | — | Ended |
| SQL Server 6.0 | June, 1995 | — | Dec, 2001 | Ended |
| SQL Server 6.5 | April, 1996 | — | Dec, 2001 | Ended |
| SQL Server 7.0 | Nov, 1998 | — | Jan, 2006 | Ended |
| SQL Server 2000 | Sept, 2000 | — | April, 2013 | Ended |
| SQL Server 2005 | Nov, 2005 | — | Jan, 2011 | Ended |
| SQL Server 2008 | Aug, 2008 | — | April, 2013 | Ended |
| SQL Server 2008 R2 | April, 2010 | — | April, 2016 | Ended |
| SQL Server 2012 | April, 2012 | — | July, 2022 | Ended |
| SQL Server 2014 | April, 2014 | — | July, 2024 | Ended |
| SQL Server 2016 | June, 2016 | — | June, 2026 | Ended |
| SQL Server 2017 | Sept, 2017 | Oct. 11, 2022 | Oct, 2027 | Extended Support |
| SQL Server 2019 | Nov, 2019 | Jan. 28, 2025 | Jan, 2030 | Extended Support |
| SQL Server 2022 | Nov, 2022 | Jan. 11, 2028 | Jan, 2033 | Mainstream |
| SQL Server 2025 | Nov, 2025 | Jan. 13, 2031 | Jan, 2036 | Mainstream |
Moser's Core Technology consultants can assess your current SQL Server footprint, flag any instances approaching Extended Support or ESU, and build a migration roadmap that fits your timeline and budget.
Do not wait for an end-of-support date to become an emergency. Talk with Moser about assessing your SQL Server environment, identifying lifecycle risk, and building a practical upgrade, migration, or support roadmap.
For organizations still running SQL Server 2016, the need to plan is especially immediate. With support now ended, businesses should be evaluating their next step, whether that means upgrading to a newer SQL Server version, moving workloads to Azure, or using Extended Security Updates as a temporary bridge. For a closer look at what SQL Server 2016 end of support means and the options available, read our guide, “SQL Server 2016 Is No Longer Supported: Is Your Business Ready for What Comes Next?”
