July 15

0 comments

Highway to the (SQL Server 2012) Danger Zone 

By Charles

July 15, 2022


As we were reporting earlier in the month, SQL Server 2012 has now officially reached it’s end of life. 

SQL Server 2012 reached its end-of-life on the 12th of July 2022 

If you are still using this version of SQL Server, you could very much be in the danger zone and unfortunately ready to crash and burn!  

End-of-life means that Microsoft will no longer be releasing hotfixes, cumulative updates or service packs and will not be providing support for any security vulnerabilities or bugs. If you are currently still using this version of SQL Server, you can see that this potentially represents huge problems for your organisation’s data and security. 
 

Talk to me, Goose 

Digital Samurai recommends that you upgrade or migrate as soon as possible to a newer version of SQL Server whether that is on-premises or in the cloud. There are lots of options that you may wish to consider, and we are here to advise on and support any potential upgrades or migrations that you need to perform. 

If you interested in the support dates for all versions of SQL Server, you could find the start dates, mainstream end dates and extended end dates here: https://docs.microsoft.com/en-us/lifecycle/products/?products=sql-server 

I’ll feel the need, the need for speed 

SQL Server 2019 is the latest version of SQL Server on general release and SQL Server 2022 will be available later this year. 

In just the last 2 weeks Digital Samurai has completed 60+ SQL Server upgrades from SQL Server 2012 and if you need assistance our team are here to help. We would love to hear about your SQL plans so feel free to get in touch. You can be our wingman anytime! 

About the author

Microsoft Certified SQL Server DBA with over a decades experience including work for large FTSE 250 companies amongst others. The SQL Server stack has been the focus of almost all of my career in IT. I have experience designing, supporting and troubleshooting large Data Platform deployments.

You might also like

{"email":"Email address invalid","url":"Website address invalid","required":"Required field missing"}
>