Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
ranvir_2k
Posting Yak Master
180 Posts |
 Posted - 2014-04-16 : 06:14:21
|
| I was wondering what most people are doing in the industry regarding SQL Server upgrades.I've got a number of SQL Server 2005 and 2008 SQL Servers that I'm planning to upgrade soon.Is it better to upgrade to 2012 or 2014?My concern with 2014 is that it has only just been released and may have issues and may not fully be reliable.Is it better to wait until the product has been released for a while? |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2014-04-16 : 19:30:02
|
| I would upgrade to 2014 if it were me and if we had the hardware for it. I would say that since SQL Server 2008 or maybe 2005 that it is safe to go with the RTM version, or at least once the first hotfix is released (not service pack).Tara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/ |
 |
|
|
jeffw8713
Aged Yak Warrior
819 Posts |
Posted - 2014-04-17 : 13:15:11
|
| Before considering either 2012 or 2014 I would validate that the application(s) and/or vendor (if vendor supplied) support that version. I have several systems that cannot be upgraded to 2012 yet because the vendor hasn't certified their application yet.I have several in-house systems that cannot be upgraded until we have time to create a 'test' environment to evaluate all of the code that would need to be changed (if any).I would never arbitrarily decide to upgrade any instance of SQL Server to a new version until it has been tested and validated on the new version. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2014-04-17 : 13:24:48
|
| Oh yes definitely needs to be tested. I definitely wasn't say to upgrade to 2014 in production without first testing it. What I am saying is that if you are planning on upgrading and can support 2014, then I would go with 2014. We have 5-6 non-prod environments. We would start with dev for the upgrade testing and then work our way through the other environments and then out to prod.Tara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/ |
|
|
|
ranvir_2k
Posting Yak Master
180 Posts |
Posted - 2014-04-20 : 16:24:06
|
| Yes obviously I would test the migration in development, test and then production.I think 2014 sounds better. Why upgrade to a lower version when a newer version is available?All of our applications are built in house by our developers so we do all the support ourselves. |
|
|
|
jackv
Master Smack Fu Yak Hacker
2179 Posts |
Posted - 2014-04-22 : 01:42:29
|
| It is not unusual for organisations to maintain the latest version - 1 (i.e 2012). There are a number of benefits: vendor certification, product support, product stability, systems management support. Overall, include in your considerations such factors as : standardisation and easy of managementJack Vamvas--------------------http://www.sqlserver-dba.com |
|
|
|
|
|
|
Upgrade to SQL 2012 or 2014