Should I Upgrade? Understanding Mainstream and Extended Support for SQL Server

“So, I’ve heard that SQL Server 2016 Extended Support expires on July 14, 2026. That doesn’t sound like a good thing, but what exactly does it mean? Can I still use my SQL Server, or do I have to upgrade? And what’s the difference between Mainstream and Extended Support anyway?”

That’s a pretty common question. Let’s look at each support phase now so that you have time to make an informed decision.

Mainstream and Extended Support

When it comes to SQL Server support, it’s crucial for businesses to understand the difference between Mainstream and Extended Support. Knowing this can help you make better decisions and keep your databases secure, reliable, and compliant.

Mainstream Support: The Prime of SQL Server

Mainstream Support is the first phase in the lifecycle of SQL Server. For about five years after its initial release, Microsoft provides comprehensive support for that product. This includes:

• Functional updates: Enhancements and modifications that improve the SQL Server’s capabilities.
• Performance improvements: Optimizations that boost the efficiency of the server.
• Scalability enhancements: Upgrades that allow SQL Server to handle larger workloads and more concurrent users.
• Reliability improvements: Stability and availability enhancements that will help strengthen SQL Server’s dependability for critical workloads.
• Security updates: Patches for vulnerabilities to keep your data protected from threats.

Mainstream Support is the golden era for any SQL Server version, where it receives the most attention and resources from Microsoft.

Extended Support: The Guarded Legacy

After the Mainstream Support phase ends, SQL Server enters the Extended Support phase, which is also about five years. During this phase, the focus shifts to security. Here’s what extended support includes:

• Security updates: Continued protection against new threats with critical security patches.

That’s a short list, right?

Unlike Mainstream Support, Extended Support does not include new features, performance enhancements, or scalability improvements. Rather, Extended Support is a period where the SQL Server version is maintained rather than evolved. Microsoft isn’t going to put a lot of work into a product that’s on its way out, so they focus on keeping the product and your data secure. This allows them to devote more development time to building future versions of the product.

Do I have to upgrade?

Do you have to upgrade before your version of SQL Server reaches or passes Extended Support?

The short answer is: No, you don’t have to upgrade. Your older version of SQL Server will continue to work after the Mainstream and Extended Support dates have passed. You won’t be in violation of a licensing agreement with Microsoft.

But… you probably should upgrade.

Why?

Why upgrade?

Staying within the Mainstream Support window keeps your SQL Server at the forefront of technology, with access to the latest features and comprehensive updates. Once in Extended Support, Microsoft’s focus is on maintaining stability and security rather than innovation, bug fixes, performance improvements, and the like.

If you’re in an industry such as banking or healthcare where compliance is a concern or you have sensitive client/patient information in your systems, staying up-to-date should be high on your priority list. So, we recommend staying within Mainstream Support if at all possible. Definitely stay within Extended Support, because continuing to use a system beyond its Extended Support period poses a significant security risk.

But what if your systems don’t house sensitive information?

Upgrading your system is still a better alternative. However, allowing it to lapse into Extended Support isn’t the end of the world. For those systems, we recommend assessing the benefits of an upgrade. For example, if your application would greatly benefit from a feature only available in a newer version, prioritize an upgrade. If not, you can schedule an upgrade sometime before the end of Extended Support.

What about applications that are scheduled to be sunsetted, where the business is shifting away from the application but needs it to remain available for some period of time afterward? For those situations, the answer is a bit less clear. Remaining on a system that is past Extended Support presents a clear security vulnerability. Yet, just how much time, effort, and money do you really want to invest in a system that’s going away? Some questions to ask: Can you make it read-only? Can you isolate it from the internet? Can you take it offline and only turn it on when/if needed? Answering those questions will influence your decision.

What next?

Understanding the distinction between Mainstream and Extended Support can help you make informed decisions about your SQL Server environment. It’s about balancing the need for innovation, security, reliability, and performance with the realities of software lifecycles.

Take an inventory of your SQL environment. What version is each SQL Server in your environment? What patch level? Which applications depend on each SQL Server?

The result will look something like the figure below. (This is from our SQL Server Health Check in our SERO Lab environment.)

Then you can determine what to do with each SQL Server instance.

Want more information? 

Deciding whether to upgrade before the end of Mainstream or Extended Support will depend on knowing the needs of your business and the status of your SQL Server environment. The following links provide additional information about SQL Server versioning.

• Is There an Update for My SQL Server?
• End of support options – SQL Server | Microsoft Learn
• Microsoft SQL Server Versions List

Concerned about your SQL Server environment? We’re here to help. Schedule a call with us to learn how a SQL Server Health Check can help provide some insight into your environment.