March 8, 2018 at 1:51 am
Our current environment is using mostly SQL Server 2014 and a few 2016 servers. We are developing a new product that is completely independent of the existing servers so I was wondering if there is any reason not to go with SQL Server 2017.
We do not have any particular requirements and we probably will be fine using SQL 2014 and the DBA's want to go with 2016. Their reasoning is SQL 2017 is relatively new and if we do not require any particular feature from 2017, it might be safer to go with 2016.
So my question, is there any reason why we should not go with SQL Server 2017? I am looking at some pointers like licensing cost or anything else that would affect the decision?
March 8, 2018 at 2:43 am
No reasons. I recommend 2017.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply