April 5, 2016 at 11:30 am
Hello experts,
We're running SQL 2012 at this point in time, but are seeking to plan a SQL upgrade for the coming year. It seems early to plan for SQL 2016 given that it is in preview as I understand it. But does anyone have any advice for which factors to consider if I am trying to decide between recommending SQL 2014 (for stability, known quantity) vs SQL 2016 (up to date, newer features)? My first inclination was to go with SQL 2014 but now I am not so sure.
Thanks for any help!
- webrunner
-------------------
A SQL query walks into a bar and sees two tables. He walks up to them and asks, "Can I join you?"
Ref.: http://tkyte.blogspot.com/2009/02/sql-joke.html
April 5, 2016 at 11:40 am
If you have a new project in development and plan to leverage some of the newer features like Clustered ColumnStore or InMemory tables, then definately go for v2016.
However, if you're simply upgrading an existing line of business application, and minimizing risk is more important than leveraging new features, then there is less of a compelling motive to wait for v2016. However, even in this case I'd still go for v2016 myself. The Microsoft MSSQL team doesn't release crap.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
April 5, 2016 at 12:22 pm
You didn't give us anything at all to go on to advise you. In particular what edition of SQL Server are you on now and are you (or could you) use any of the new features of 2016 (std or enterprise)?
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
April 5, 2016 at 12:49 pm
I'd recommend 2016. We're at RC2 at this point, gut feel we'll see RTM late this month, maybe next month.
2016's got a lot of interesting new stuff in it, Query Store is the best new feature as far as I'm concerned (no more 'how did the query run last week' problems), Temporal tables, stretch tables (though not so compelling with the new pricing model for the Azure part), etc.
You'll need to do extensive testing no matter which version you upgrade to, because 2014 got the new cardinality estimator and while my experience has been that most queries either stay the same or get minor performance improvements, there will be a handful that get degraded performance from the new cardinality estimator.
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
April 5, 2016 at 12:57 pm
Upgrading to 2014 or 2016 is basically an identical amount of labor. With that in mind, I'd go for 2016. Yeah, it's newer, it might be a little rocky in parts as a new release. Although I've been working with it for... a while lets say, and it has been rock solid. When you take into account how long it's going to take you to do all the testing for a production rollout, CU1 or CU2 will be out, and you'll be safe.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 6, 2016 at 9:31 am
TheSQLGuru (4/5/2016)
You didn't give us anything at all to go on to advise you. In particular what edition of SQL Server are you on now and are you (or could you) use any of the new features of 2016 (std or enterprise)?
Thanks -
I intentionally limited my initial question in order to elicit the most basic opinions regarding SQL versions given the current state of SQL 2016, which as I understand is still early although as others have stated seems to be mature enough for many shops. But I appreciate your comment and will add some more details.
We are on a combination of editions - SQL 2012 Enterprise Edition for our main servers, SQL 2012 Standard on the servers that are not the main servers, as well as a mix of clusters and standalone servers.
For this particular round of upgrades we are interested in upgrading only the Enterprise Edition servers, so I can check to see whether SQL 2014 Enterprise or SQL 2016 Enterprise has the features that we can make use of.
I guess my fundamental concern is in trying to avoid "buyer's remorse" while planning an upgrade a year in advance, and trying to gain the most from the upgrade decision I do end up recommending. So I am curious what factors the DBAs here are using to pick between SQL 2014 and SQL 2016 and whether I can pick their brains to use similar factors for myself. 🙂
Thanks again.
- webrunner
-------------------
A SQL query walks into a bar and sees two tables. He walks up to them and asks, "Can I join you?"
Ref.: http://tkyte.blogspot.com/2009/02/sql-joke.html
April 6, 2016 at 9:34 am
Thanks to everyone for their answers! I know your answers are not intended to say "you should go to SQL 2016," but I appreciate the feedback consensus, which I did not know, that even at this stage SQL 2016 is mature enough, certainly for an upgrade a year out. I will take this information back and reconsider my original plan for SQL 2014.
Thanks again!
- webrunner
-------------------
A SQL query walks into a bar and sees two tables. He walks up to them and asks, "Can I join you?"
Ref.: http://tkyte.blogspot.com/2009/02/sql-joke.html
April 7, 2016 at 1:19 pm
I would certainly aim for SQL 2016. You are at the start of your planning, so no way will you be ready to go live before SQL 2016 is RTM. As others have said, the work needed to go to SQL 2016 is just about the same as for SQL 2014, so you have nothing to loose by choosing SQL 2016.
Whatever version of SQL Server you upgrade to, you will be keeping it for probably three years. You might not need JSON support on day 1, but by the end of this year your developers will be thanking you if you chose SQL 2016 and complaining if you chose SQL 2014. Your analytics users will thank you for the R support if you choose SQL 2016, but might not notice the loss if you choose SQL 2014.
Going for SQL 2016 at this stage means you will be ready for when the business needs the new facilities.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
April 7, 2016 at 3:52 pm
Great, thanks for your advice on this!
- webrunner
-------------------
A SQL query walks into a bar and sees two tables. He walks up to them and asks, "Can I join you?"
Ref.: http://tkyte.blogspot.com/2009/02/sql-joke.html
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply