December 4, 2014 at 9:43 am
Is upgrading from SQL Server 2008 R2 and 2005 to SQL Server 2014 better then going to 2012?
I know that 2014 is at RTM but their are CU's out.
The cost seems better for us since it is based on CALS.
I heard that it did not have many improvements for developers.
I also read that there were some issues with the size of the transaction Log?
It appears to have better memory performance and is is oriented towards OLTP as opposed to OLAP?
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
December 4, 2014 at 11:09 am
Welsh Corgi (12/4/2014)
Is upgrading from SQL Server 2008 R2 and 2005 to SQL Server 2014 better then going to 2012?I know that 2014 is at RTM but their are CU's out.
True, but it is quite stable in my experience so far
The cost seems better for us since it is based on CALS.
Love to save some dough!
I heard that it did not have many improvements for developers.
true, except support for VS 2013
I also read that there were some issues with the size of the transaction Log?
haven't heard about that or seen it so far. Link?
It appears to have better memory performance and is is oriented towards OLTP as opposed to OLAP?
Not so much orientation, but 2014 has enhancements that directly benefit OLTP. See here: http://msdn.microsoft.com/en-us/library/bb510411.aspx
Sounds to me like you should install 2014 AND 2012 and do some testing with your most demanding apps. If there is no clear winner, choose 2014.
Gerald Britton, Pluralsight courses
December 4, 2014 at 12:02 pm
Everything I've done and heard suggests that 2014 is basically a more stable 2012 with many of the improvements of 2012 polished, including more stability in Availability Groups, better behavior of columnstore indexes and a whole bunch of other improvements. Yeah, some of the newest stuff like in-memory tables are somewhat limited, but all the rest is very much ready for primetime. I'd go for 2014 over 2012 if I were looking to move now.
"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
December 4, 2014 at 12:07 pm
I appreciate the information.
Thank you.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
December 5, 2014 at 2:37 am
At this point I'm recommending that clients on 2005/2008/2008 R2 upgrade to SQL 2014 and for clients on SQL 2012 to stay put unless there's a compelling feature they absolutely need.
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 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply