The Final Countdown for SQL Server 2012 Extended Support

If you haven’t already done so, the time has come to say goodbye. In just six short months, SQL Server 2012 Extended Support will come to an end. And although it’s been a good version, it’s 10 years old. And that’s old database in years.

To put it into context, here are a few other things from the 2012 era.

• U.S. President Barak Obama was elected to his second term in office.
• The Curiosity Rover landed on Mars.
• Marvel’s The Avengers became one of the highest grossing films released.

And from a technology perspective in 2012,

• Windows Phone 8 was unveiled
• Raspberry Pi Model A version sold for $25
• The iPhone 5 was released.

Feeling old yet?

Some FAQs for SQL Server 2012 Extended Support

SQL Server 2012 brought with it some cool features. Columnstore indexes, contained databases, and enhanced PowerShell support got the SQL Server community really excited. The follow up to the confusingly named SQL Server 2008 R2 also had HADR features, like Always On Availability Groups and Always On Failover Clustered Instances. These features have been carried forward in subsequent versions of SQL Server.

Now that we’re in the final T-minus 6 months for SQL Server 2012 Extended Support, we should determine what to do with those old but beloved instances.

Here are a few Frequently Asked Questions that may help.

What does Extended Support really mean, anyway?

According to Microsoft’s web site, Lifecycle Terms and Definitions – Microsoft Lifecycle | Microsoft Docs, during the extended support phase a product may still receive some security updates, but that’s really about it. Sure you can call Microsoft and pay for support or request a non-security fix, but those things aren’t proactively provided. And you’ll need to have a credit card ready.

So, for the most part, you’ll have what you have now. Don’t expect bugs to be fixed, or performance enhancements to be made. You may receive an occasional hotfix to address a security concern. But that’s probably it.

Once Extended Support has ended on July 12, 2022, the security hotfixes and updates go away too.

Do I have to upgrade my SQL Server 2012?

No. You don’t have to upgrade. The ability to run SQL Server 2012 in your production environment won’t go away on July 12, 2022. You won’t violate your EULA (End User Licensing Agreement) if you keep those SQL Servers running for another year or two past July 12, 2022.

However, it’s not uncommon for application vendors to drop support for older versions of SQL Server. For example, your Electronic Medical Records application or your financial and accounting packages may require you upgrade your SQL Server systems.

Plus, running on an older version of SQL Server could be risky for other reasons. See Why Not Upgrading Could Be Risky for Your Data for more info.

What are some options for my SQL Server 2012 instances?

You’ve got options. Here are six.

1. Do nothing.
2. Upgrade each SQL Server 2012 instance to a newer version.
3. Consolidate your SQL Server 2012 instances into fewer but newer instances.
4. A combination of numbers 3 and 4.
5. Move your SQL Server 2012’s to Azure and receive additional time. (Free Extended Security Updates only on Azure for Windows Server 2012 /R2and SQL Server 2012 | Azure updates | Microsoft Azure)
6. As a last resort, you can check into Microsoft’s Extended Security Update (ESU) Program.

See 4 Options Now That Your SQL Server 2008 Is Out of Support for a discussion of these options.

Should I upgrade to SQL Server 2016?

I wouldn’t recommend upgrading to SQL Server 2016. It’s already out of Mainstream Support. See End of Mainstream Support for SQL Server 2016, so you’ll likely face another upgrade in the next couple of years if you go this route.

If you’re going to upgrade, I’d recommend going to a newer version, like SQL Server 2019.

Should I upgrade now? Or wait for SQL Server 2022?

That’s a great question. Upgrading a single instance can be relatively straightforward. But that’s not always the case. Upgrading multiple instances running different applications can magnify the effort required. How much effort really depends on your environment.

I talk about some of the factors in in this post – Should I Upgrade Now? Or Wait for SQL Server 2019? The same factors apply.

• How many SQL Server instances must be upgraded? 
• How long will it take to upgrade the instances?
• Are there compelling reasons or features in the newest version that would influence your decision?
• Will your application vendor support SQL Server 2022 soon?
• How much testing must be done before upgrading? 
• How long will the new hardware and/or virtual machines take to requisition? 
• Are the database servers so critical that being on the “bleeding edge” is undesirable?

What should I do first?

If you’re considering an upgrade, run the Data Migration Assistant. It checks to see if you’re using any features that may have been deprecated in later versions of SQL Server.

If all looks good, then build your upgrade project plan. Don’t forget a step to test performance. Often the newer version will help performance. But not always. Better to know and adjust/tune before the upgrade.

Should I do an in-place upgrade, or a side-by-side?

Side-by-side. Install a new copy of SQL Server on a new VM and migrate the databases, logins, etc, from your SQL Server 2012 instance to the new instance.

Test and when you’re satisfied, then you can make the final migration.

Want some help?

We do this kind of thing for a living. And we’ll be happy to help with your SQL Server upgrade.  Schedule a call and learn more.