April 10, 2014 at 3:32 pm
Hi All,
It has been a while since I came here...
We are starting to talk to migrate some SQL2005 and possibly 2008. Will you recommend SQL2012 or 2014? I've not see or hear much yet about SQL2014.
Thanks,
Rem
April 10, 2014 at 9:31 pm
I would recommend to test SQL 2014 before implementing it. No doubt SQL 2014 gives a boost in performance through it's new In memory OLTP engine, however there are certain conditions to move a table into in OLTP memory engine.
I did performance testing on SQL 2014 on it's new In memory OLTP and found it really interesting.
Regards,
Ashif Shaikh
April 11, 2014 at 1:43 am
Difficult to answer that really. If you could make use of the new features in 2014 and aren't a particularly risk-averse company, test it and go with that.
If you're a more conservative organisation that won't really make immediate use of the 2014 features, then 2012 is pretty stable and has had a huge number of bug fixes added since RTM.
2014 will have some (but not all) of these bug fixes, but will obviously have new code on top that potentially will have bugs exposed when it starts getting used in anger.
I have to say, I used to ignore the "wait until SP1" dogma, but SQL 2012 has been quite a rough ride in terms of bugs since RTM so I'm more cautious these days. I'd be considering licensing for 2014 on new environments, but deploying 2012, planning in an upgrade next year.
April 11, 2014 at 3:48 am
If your application supports and all testings are OK than you should go with SQL Server 2014. There are advantage of new features of SQL 2014 and also it will put you 2 years ahead i.e. if you use 2014 which will sustain server few more years with upgrade. As a DBA you are the best judge to migrate your server to 2012 or 2014?
HTH
---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
April 11, 2014 at 4:23 am
Most of the migration projects I've been on take 6-9 months to move stuff over. With that in mind, I usually always suggest going to the latest release because we're then well past the first 6-8 weeks when everything breaks if it's going to. Also, it extends the support life of the product by at least two years.
"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
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply