Another SQL Product End of Support??
We have reached the end of another SQL Server product life cycle from a support standpoint. I remember when SQL Server 2012 came out. It was a very exciting release since we had waited over four years for this release to arrive. Not only that, but we were also getting some really helpful features that made this a version people were taking a good look at.
Because of this, there are many companies using SQL Server 2012 still to this day. In this article, we will walk you through the options that you have with SQL Server 2012. Everything from staying on the platform to where should we go next?
What is End of Support?
From a Microsoft perspective, end of support means that regular security updates will no longer be provided for SQL Server 2012. With cyberattacks becoming more sophisticated and frequent, running apps and data on unsupported versions can create significant security and compliance risks. It is highly recommended that customers upgrade to the most current versions for better performance, efficiency, and regular security updates.
What options do I have if I can’t move away from SQL Server 2012?
Microsoft has given customers an option, similar to SQL Server 2008 End of Support, where you can migrate your SQL Server Databases to an Azure SQL VM, running SQL Server 2012, and be supported for 3 additional years after the End of Support date (July 12, 2022). This is a great options for customers who are facing “Vendor Lock In” and can’t move away from a specific version of SQL Server for support reasons.
What if I don’t want to go to Azure?
If your workloads are not ready for Azure, or if Azure isn’t the cloud you want to consider, your path should be to consider an Upgrade to a supported version of SQL Server. Ideally moving to a platform that is the latest technology makes the most sense. Considering SQL Server 2019 is the best idea for avoiding the problems of having to upgrade every year.
Staying on SQL Server 2012 past the end of support date is not a great idea, because it puts your company and your data at risk.
Why not use Compatibility Levels?
One area we are trying to get customers focused in on is taking advantage of Compatibility Levels. SQL Server has had this concept for over 20 years now, but very few application developers are taking advantage of it. Currently, many application developers are still focused on what Version of SQL Server and what Service Pack/CU to get support from vendors. This is a very limiting method of approving versions of your database engine.
The vision that application developers should be taking is to look at Compatibility Level of a database as their stamp of approval. By doing this, you open a much larger arena for your customers and really take the stress off supportability. This can also open the doors for cloud capability and much smoother mobility to give your customers good options.
Microsoft has a great article to get you thinking about Compatibility Certification:
We are here to help guide you!
We have been through hundreds of these conversations about “what do we do next” and would be happy to talk through any of your questions. Reach out to us for a complimentary 1 hour conversation.