none
I'm really not that tech savvy.

    Question

  • Should I even be trying to upgrade SQL from 2005 to 2012? Can I do any real harm by messng it up?

    Is there an easy way to do it?


    Edit: Thanks for any help and consideration. I'm really lost with this!
    • Edited by cewubaaca Saturday, June 22, 2013 10:06 AM courtesy
    Saturday, June 22, 2013 9:57 AM

Answers

  • Should I even be trying to upgrade SQL from 2005 to 2012? Can I do any real harm by messng it up?

    Is there an easy way to do it?


    Edit: Thanks for any help and consideration. I'm really lost with this!

    Yes you should upgrade to  SQL server 2012 it has far better capabilities and is much more improved from SQL server 2005 also 2005 is old now and in couple of years support is going to end..many new features related to HA and Query tuning are added in sql server 2012.

    You first need to check your application compatibility with 2012 them migrate ur DB to 2012>two types of upgrades

    1.In place

    2. Side by side..( i prefer this)

    refer to below doc it lenghty but look for section dealing with upgrade

    http://social.technet.microsoft.com/wiki/contents/articles/7009.sql-server-2012-upgrade-and-application-compatibility.aspx

    When u upgrade side by side

    1. You install SQL server 2012 edition on server

    2. U check ur application compatibility with SQL server 2012

    3. You backup db from sql 2008 r2 and restore on it

    4. You transfer logins and packages by taking script (see for orpahned users)

    For inplace upgrade run upgrade advisor look for errors/constraints resolve it and upgrade it ,you run set.up.exe and in install section u look for upgrade and click that link to upgrade ur instance

    Few links for ur help

    http://msdn.microsoft.com/en-us/library/ms144267.aspx

    http://www.google.co.in/url?sa=t&rct=j&q=upgrade%20sql%20serer%202005%20to%202012&source=web&cd=3&cad=rja&ved=0CDgQFjAC&url=http%3A%2F%2Fdownload.microsoft.com%2Fdownload%2F9%2F5%2F3%2F9533501A-6F3E-4D03-A6A3-359AF6A79877%2FSQL_Server_2012_Upgrade_Technical_Reference_Guide_White_Paper.pdf&ei=zXjFUeHLBoHprQeWr4HwBQ&usg=AFQjCNGkAVIR2vx0T52CugXZKPM-sTUnLA&bvm=bv.48293060,d.bmk


    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers


    • Edited by Shanky_621 Saturday, June 22, 2013 10:19 AM added line
    • Proposed as answer by Keith Langmead Saturday, June 22, 2013 3:22 PM
    • Marked as answer by cewubaaca Saturday, June 22, 2013 4:00 PM
    Saturday, June 22, 2013 10:17 AM
  • Completely agree with Shanky, especially regarding using the backup and restore method to upgrade rather than in place. It's so much easier and less stressful when you know if it goes wrong you can switch back to your old working setup.

    As someone who's just recently upgraded SQL 2005 and SQL 2000 setups to 2012 I'd add a couple of other points though.

    1. To migrate the user logins (especially if you have SQL logins on there and you want to transfer the existing passwords) check out http://support.microsoft.com/kb/918992. One thing to note (and this caught me out) I don't believe the script handles language, so all logins are created using the default. So if like me you have a combination of English and British English users you'll need to check and possibly update that afterwards.

    2. Compatibility levels only go back two old versions. If you upgrade to 2012 now the databases will maintain their 2005 compatibility level until you change them, but if you for instance wait until SQL 2014 is out then 2008 will be the oldest supported, and when they're migrated they'll automatically be upgraded to 2008 compatibility level, at which point any issues could cause you issues. With 2012 it's also only possible to upgrade (by whatever method) by two versions, so if the same is true with 2014 you'll find you need to upgrade to 2008 or 2012 first before going to 2014.

    3. 2012 is definitely a big improvement on 2005, but in terms of usability SSMS is very similar in all important aspects, eg everything you can do now you'll easily be able to do on 2012, you'll just have some more options available to play with.

    • Marked as answer by cewubaaca Saturday, June 22, 2013 4:00 PM
    Saturday, June 22, 2013 3:13 PM

All replies

  • Should I even be trying to upgrade SQL from 2005 to 2012? Can I do any real harm by messng it up?

    Is there an easy way to do it?


    Edit: Thanks for any help and consideration. I'm really lost with this!

    Yes you should upgrade to  SQL server 2012 it has far better capabilities and is much more improved from SQL server 2005 also 2005 is old now and in couple of years support is going to end..many new features related to HA and Query tuning are added in sql server 2012.

    You first need to check your application compatibility with 2012 them migrate ur DB to 2012>two types of upgrades

    1.In place

    2. Side by side..( i prefer this)

    refer to below doc it lenghty but look for section dealing with upgrade

    http://social.technet.microsoft.com/wiki/contents/articles/7009.sql-server-2012-upgrade-and-application-compatibility.aspx

    When u upgrade side by side

    1. You install SQL server 2012 edition on server

    2. U check ur application compatibility with SQL server 2012

    3. You backup db from sql 2008 r2 and restore on it

    4. You transfer logins and packages by taking script (see for orpahned users)

    For inplace upgrade run upgrade advisor look for errors/constraints resolve it and upgrade it ,you run set.up.exe and in install section u look for upgrade and click that link to upgrade ur instance

    Few links for ur help

    http://msdn.microsoft.com/en-us/library/ms144267.aspx

    http://www.google.co.in/url?sa=t&rct=j&q=upgrade%20sql%20serer%202005%20to%202012&source=web&cd=3&cad=rja&ved=0CDgQFjAC&url=http%3A%2F%2Fdownload.microsoft.com%2Fdownload%2F9%2F5%2F3%2F9533501A-6F3E-4D03-A6A3-359AF6A79877%2FSQL_Server_2012_Upgrade_Technical_Reference_Guide_White_Paper.pdf&ei=zXjFUeHLBoHprQeWr4HwBQ&usg=AFQjCNGkAVIR2vx0T52CugXZKPM-sTUnLA&bvm=bv.48293060,d.bmk


    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers


    • Edited by Shanky_621 Saturday, June 22, 2013 10:19 AM added line
    • Proposed as answer by Keith Langmead Saturday, June 22, 2013 3:22 PM
    • Marked as answer by cewubaaca Saturday, June 22, 2013 4:00 PM
    Saturday, June 22, 2013 10:17 AM
  • Completely agree with Shanky, especially regarding using the backup and restore method to upgrade rather than in place. It's so much easier and less stressful when you know if it goes wrong you can switch back to your old working setup.

    As someone who's just recently upgraded SQL 2005 and SQL 2000 setups to 2012 I'd add a couple of other points though.

    1. To migrate the user logins (especially if you have SQL logins on there and you want to transfer the existing passwords) check out http://support.microsoft.com/kb/918992. One thing to note (and this caught me out) I don't believe the script handles language, so all logins are created using the default. So if like me you have a combination of English and British English users you'll need to check and possibly update that afterwards.

    2. Compatibility levels only go back two old versions. If you upgrade to 2012 now the databases will maintain their 2005 compatibility level until you change them, but if you for instance wait until SQL 2014 is out then 2008 will be the oldest supported, and when they're migrated they'll automatically be upgraded to 2008 compatibility level, at which point any issues could cause you issues. With 2012 it's also only possible to upgrade (by whatever method) by two versions, so if the same is true with 2014 you'll find you need to upgrade to 2008 or 2012 first before going to 2014.

    3. 2012 is definitely a big improvement on 2005, but in terms of usability SSMS is very similar in all important aspects, eg everything you can do now you'll easily be able to do on 2012, you'll just have some more options available to play with.

    • Marked as answer by cewubaaca Saturday, June 22, 2013 4:00 PM
    Saturday, June 22, 2013 3:13 PM
  • thanks, both Keith & Shanky.

    You have answered my question perfectly! Given that I have no idea what either of you were going on about at all, you might as well have been writing in Sanskrit!

    Not your fault, entirely mine, I now know that I should pay someone else to do this!

    Regards & thanks again :-)

    Charlie

    Saturday, June 22, 2013 3:22 PM