Dec 26, 2017 2:00:37 PM by Denny Cherry
There’s a lot of versions of SQL Server available today. I’ve seen clients deploying new services on SQL Server 2015, SQL Server 2016, SQL Server 2017 (yes we have a client on SQL Server 2017 already) and SQL DB. But if you’re deploying a new SQL Server what’s the right version to deploy?
I’d love to tell you that the answer is to use the newest version, but it isn’t. And no one should.
Our first thing to look at is what features of the database platform do we need. Do they require SQL Server 2017 or does it work with older versions of SQL Server? The next decision point is what versions is the DBA ready to support? Our customer that is running SQL Server 2017 is willing to be on the bleeding edge of technology and take risks with new versions of software within days of their release. Not everyone is willing to take these risks and feel more comfortable on SQL Server 2014 or SQL Server 2016. While I don’t always agree with the idea of running older versions, for this reason, I do understand it. I may agree with it, but I do understand it.
After that, it before a political decision within your company as to what version of the database to run. I can’t help much with political problems.
If possible, I’d vote for a newer version, but my vote isn’t usually the important one.
Tags: SQL Server
Written by Denny Cherry
I am a Senior SQL Server DBA at CDW with 10 years of IT experience, mostly as a software developer building web and windows based applications (VB, VB.NET, C#, C++ and a smidge of Java). I have always found database design and set based logic interesting, so 3 years ago I took the plunge and became a DBA, soon after I discovered people would tell anyone who would listen all about the SQL Server internals. I was hooked. I have not looked back since. The things I say represent my opinion and in no way represent the views or opinions of my employer or coworkers.