SQL Server and SQL Server Compact is Microsoft’s relational database management system (RDMS) application. As its name suggests, it is used to manage the databases you use for your business. SQL Server 2014 went End of Life on July 9, 2024. But no worries because we got you covered with this guide.
⚡ TL;DR | Go Straight to the SQL Server End of Life Audit
Microsoft outlines the end-of-life dates for all of their products to make customers aware of when they will cease support for specific products. SQL Server is no exception to this. Each version of SQL Server usually has both an end of support date and an end of extended support date.
Why should I care?
At the end of mainstream support, Microsoft will no longer provide non-security hotfixes unless you have an extended support agreement. All warranty claims end and they will no longer accept feature and change requests.
Once a product reaches its ‘Extended Support End Date’ there will be no patches, security updates or support from Microsoft. Without upgrading to a supported version of SQL server, organizations are at significantly more risk due to future vulnerabilities remaining unpatched. They might also break data protection and security compliance which dictates that technologies used must be supported. Lastly, it can cause compatibility, reliability and performance issues as newer technologies will rely on modern SQL server features to function.
71% of SQL Server Installations Are Past Their Mainstream Support Date
We recently took a closer look at over 500 thousand SQL servers installations. In total over 71% are using an SQL server which is already is in an extended end-of-life phase (SQL Server 2017 or lower). However, there are options to continue using these SQL Server versions by purchasing Extended Security Updates (ESU). This number doesn’t even include SQL Server 2019 which left its mainstream support date on February 28, 2025.
We seen a rapid shift to SQL Server 2019 which now has a significant lead at 29% being the most popular SQL Server version by far. Even with a fast migration, SQL server 2017 and SQL Server 2014 remain at 17%, a not so insignificant number if installations that are at risk of no longer receiving security updates if organizations are not aware of the SQL Server 2014 and 2017 lifecycle and do not migrate or purchase the ESU.
Without upgrading to a supported version of SQL server, organizations risk additional exposure to cyberattacks, losing compliance with data protection and security compliance and losing productivity, compatibility and reliability.
SQL Server 2019 End of Mainstream Support
SQL Server 2019 will reach the end of mainstream support on February 28, 2025. After this date, Microsoft will stop providing regular updates, bug fixes, and non-security patches. However, extended support will continue until January 8, 2030, ensuring that critical security updates remain available.
For organizations still using SQL Server 2019, now is the time to start planning for the future. One recommended upgrade path is SQL Server 2022, which offers improved performance, security enhancements, and expanded cloud integration capabilities. Migrating to a newer version ensures continued support, access to new features, and better long-term stability.
SQL Server 2014 End of Life
SQL Server 2014 reached its extended end-of-life on July 9, 2024. After just over 10 years, the only available supported way to continue using SQL Server 2014 was by purchasing an Extended Security Updates (ESU) subscription, which could add an additional 3 years of support. This means that it is possible to extend support until 2027 for those willing to pay.
According to our data, 17% of SQL servers are still running SQL Server 2014 and require the ESU subscription or need to be upgraded to a newer supported version of SQL Server.
SQL Server 2012 End of Life
SQL Server 2012 officially reached end-of-life on July 12, 2022, after being supported for over 10 years. While it is recommended to migrate databases to a newer SQL Server version, it is still possible to remain on SQL Server 2012 by purchasing the Extended Security Update (ESU) package. This package allows organizations to buy up to 3 additional years of support in case they were not yet prepared for a migration.
SQL Server 2008 and 2008 R2 End of Life
SQL Server 2008 and SQL Server 2008 R2 reached their end of support on July 9, 2019, while Windows Server 2008 and Windows Server 2008 R2 met their deadline along with Windows 7 on January 14, 2020. Organizations that were still using these SQL Server versions had the option to purchase Extended Security Update (ESU) packages, which extended end-of-life support until July 12, 2022. For those needing an additional year of support, the only option was to use the Azure version, which received a 4th extended security update year.
The Microsoft Lifecycle Policy provided a total of 10 years of support—5 years of Mainstream Support and 5 years of Extended Support—for the 2008 and 2008 R2 versions of SQL Server and Windows Server.
Run the SQL Server End of Life Audit Report
Our SQL Server End of Life Audit provides an overview of all the SQL Server installations in your network along with an indication of whether they have surpassed their extended support date.
After the extended support date has passed, your SQL Servers might no longer be secure as they will not receive security updates. It’s highly recommended that if you have SQL servers that reached or surpassed their end-of-life date, you update them as soon as possible.
Want to run this Audit Report?
Start your Free Lansweeper Trial to run the Audit Report.
Try for FreeSQL Server Compact End of Life
SQL Server Compact 4.0 goes end of life on July 13, 2021. What does this mean for you? Well, there will be no more security updates or patches and technical support. That’s why we at Lansweeper made a custom SQL Server Compact EOL report to help you audit your network to detect outdated installations.
What are my options?
Simply put:
- Pay for Extended Security Updates
- Update to a more recent version of SQL Server
- Migrate to Microsoft Azure
Extended Security Updates
The easiest thing to do if your organization has missed an EOL deadline is purchasing Extended Security Updates from Microsoft. These security updates include critical and important security updates, but no new features, or customer-requested non-security updates. Additionally, purchasing extended support is a very costly, very temporary solution.
This is an option that is available to clients using SQL Server or Windows Server with an active license, although it’s merely postponing troubles.
Upgrade to SQL Server 2019
Another path forward is to simply upgrade to more recent versions of these products: SQL Server 2019. By upgrading your installations, you’ll have access to updates for multiple years.
Migrate to Azure
The main recommendation is migrating the on-premise Microsoft SQL workloads into the Microsoft Azure cloud. Through upgrading legacy on-premise database technology, businesses consolidate their environment and optimize performance, recovery, and provisioning.
The cloud is evergreen and allows you to scale up or down as required, paying only for what you consume. Exchange Online, as part of Office 365 or Azure SQL Database, are great examples of Microsoft’s modern approach to mainstream server applications.
Microsoft states that with a minor change within the code, you can host SQL Server 2008 or SQL Server 2008 R2 to an Azure SQL database.
SQL Server EOL Overview
| Version | EOL Date | Extended security update option? |
| Microsoft SQL Server 2005 | Apr 12, 2016 | No |
| Microsoft SQL Server 2008 | Jul 9, 2019 | Jul 12, 2022 Jul 11, 2023 (Azure only) |
| Microsoft SQL Server 2008 R2 | Jul 9, 2019 | Jul 12, 2022 Jul 11, 2023 (Azure only) |
| Microsoft SQL Server 2012 | Jul 12, 2022 | Jul 8, 2025 |
| SQL Server 2014 | Jul 9, 2024 | No |
| SQL Server 2016 | Jul 14, 2026 | No |
| SQL Server 2017 | Oct 12, 2027 | No |
| SQL Server 2019 | Jan 8, 2030 | No |
| SQL Server 2022 | Jan 11, 2033 | No |
