Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Upgrade to 2008 - Some Advice Expand / Collapse
Author
Message
Posted Wednesday, February 13, 2013 6:24 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Sunday, February 17, 2013 5:40 PM
Points: 153, Visits: 172
Hi,

I was just wondering what the best option is. I have a 2005 SQL server with 4 instances and about 30 databases that I want to upgrade to 2008.

I was wondering if it's best to uninstall the 2005 SQL instances or just upgrade to SQL 2008 over the top.

Thanks
Kris



Thanks,

Kris
Post #1419788
Posted Thursday, February 14, 2013 1:35 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Friday, April 12, 2013 3:51 AM
Points: 5,075, Visits: 4,831
Best option is a side by side install upgrade, that is if you have a spare server or can change the connection strings and have 4 2008 instances running along side your 2005 instances.

You could do an inplace upgrade, but would have to do it 4 times, one for each instance.

You could uninstall reinstall, but you would have to ensure that you have scripted all server wide objects, jobs, ssis packages etc etc out so that they can be recreated once you reinstall.

Also remember before doing anything take a full backup of all the databases, and always do it on a test environment to get a feel for the problems which may arise during the pre and post upgrade steps.




Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1419864
Posted Thursday, February 14, 2013 5:00 AM


SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Today @ 3:54 AM
Points: 449, Visits: 353
anthony.green (2/14/2013)
Best option is a side by side install upgrade, that is if you have a spare server or can change the connection strings and have 4 2008 instances running along side your 2005 instances.

You could do an inplace upgrade, but would have to do it 4 times, one for each instance.

You could uninstall reinstall, but you would have to ensure that you have scripted all server wide objects, jobs, ssis packages etc etc out so that they can be recreated once you reinstall.

Also remember before doing anything take a full backup of all the databases, and always do it on a test environment to get a feel for the problems which may arise during the pre and post upgrade steps.


+1 for anthony's response.

When I upgraded one of our older servers from 2005 to 2008 R2 I installed the new 2008 instance on another server so that we could verify everything before finally wiping the old server so it could be redeployed as a mirror witness.

I'd definitely recommend thorough testing before going live though..... test, test, test!!



MCITP
MCTS - E-Business Card
Twitter: WWDMark

Try not! Do or do not, there is no try

email: info@weekendwebdesign.co.uk
Website: www.weekendwebdesign.co.uk
Post #1419988
Posted Thursday, February 14, 2013 5:42 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Thursday, May 16, 2013 6:44 AM
Points: 1,856, Visits: 528
I also agree with Anthony completely. When we upgraded from 2005 to 2008, we installed it on a separate physical server and tested everything. I will say it again - test everything! We're in the process now of bringing another database server online. We're going to follow the same process - migrate copies and test everything.

It'll also give you time to address any problems you find on the new server without having your production environment down while you work.
It's a proven approach and gives you a fallback position if you have to abandon.
Post #1420001
Posted Thursday, February 14, 2013 4:45 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Sunday, February 17, 2013 5:40 PM
Points: 153, Visits: 172
Unfortunately I don't have the luxury of another server hence the question. In a perfect world I'd build a new server and then move the databases one by one.

Thanks for the comments, it's food for thought



Thanks,

Kris
Post #1420343
Posted Thursday, February 14, 2013 5:00 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Today @ 8:56 AM
Points: 1,320, Visits: 1,773
Have to admit, I just upgrated in place from SQL 2005 to 2008. It's fairly straightforward. (Nothing at all like the huge changes going from SQL 2000 to 2005.)

SQL DBA,SQL Server MVP('07, '08, '09)
One man with courage makes a majority. Andrew Jackson
Post #1420348
Posted Friday, February 15, 2013 8:36 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Sunday, February 17, 2013 5:40 PM
Points: 153, Visits: 172
I must be doing something wrong. When I go to upgrade in only upgrades the Configuration Tools. It won't upgrade the current instances of SQL server. Or it wants to create a new instance.

Thanks
Kristen



Thanks,

Kris
Post #1420852
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse