64-bit upgrade checklist

Question

64-bit upgrade checklist

Indianrock

SSC-Insane

Points: 20333
More actions
July 29, 2010 at 2:04 pm

#141483

I know I've scripted out logins and sql agent jobs before, but this upgrade will probably create new master and msdb databases ( new server boxes ) so I'll have to know that detaching and then reattaching the user databases after the upgrade will put them back into the various filegroups etc as they exist today.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Indianrock SSC-Insane Points: 20333 More actions · Answer 1

Here is the checklist so far. I'd also like to figure out how to save or script out my database mail configuration. The 64-bit install will be on a new sql boxes, replacing the existing ones. ( active/passive cluster )

1. Script out logins, linked servers, etc and document all maintenance plans and sql agent jobs

2. Script out any stored procedures, functions or custom code from master database since we won't be restoring that - we'll have a new blank one from the install. Any such code in user databases will be restored when the DB is re-attached.

3. Document filegroups and file locations for <main client database>

4. Back up all databases

5. Stop any service that will access user databases including sql agent

6. Detach user databases including msdb ( contains sql agent jobs etc)

7. System is taken down - OS and sql server are upgraded to 64-bit ( sql 2005)

8. Once system is up, re-attach user databases: For msdb -- may have to restore msdb from backup since the new installation will have a blank msdb Make sure <main client database> goes into the correct filegroups/luns etc.

9. Apply logins from script and code saved from master database

10. Verify sql jobs and possibly run checkdb

11. Start all services - test.

mmacalos Grasshopper Points: 17 More actions · Answer 2

I'm doing a similar upgrade from 32-bit 2005 running on a 64-bit OS to 64-bit 2008 running on the same OS.

I had planned to script out all of my msdb jobs and rebuild my proxies.

Can anyone verify that restoring a 2005 msdb over a 2008 msdb works fine?

I wonder about SSIS packages and such.

Thanks for any assistance.

Lowell SSC Guru Points: 323518 More actions · Answer 3

and post upgrade, to address how statistics are used differently in the updated sql engine:

1. rebuild all indexes.

2. UPDATE STATISTICS [EachTableName] WITH FULLSCAN

nothing worse than to upgrade to a monster server and hear everyone whine that the old one was faster.

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!