February 19, 2009 at 12:34 pm
Hi,
We are doing side-by-side upgrade to sql server 2005. For this We are planning to go with below plan.
Please correct us if we are going in wrong way and the order of the steps
1. Backup the databases in Sql server 2000.
2. Run Upgrade advisor and resolve blocking issues if any.
3. Install sql server 2005, SP3, sqlserver2005_dts.msi
4. Restore the backups in newly installed sql server 2005.
5. DBCC for DATA_PURITY
6 switch to dblevel 90
7 rebuild all indexes (individually)(COuld you please tell me what to do in this step)
8 dbcc updateusage with count_rows
9 sp_updatestats
10. Script the logins,jobs in sql 2000
11.Run scripted logins and jobs in sql server 2005(Iam not sure whether it is done before restoring the backups or not)
12. create a new backup
13. perform test by the application team(s)
Please advice me about the correct order of the steps from above
Thanks
Kotla
February 19, 2009 at 4:54 pm
personally i would use
1. Backup the databases in Sql server 2000.
2. Script the logins,jobs in sql 2000
3. Install sql server 2005, SP3, sqlserver2005_dts.msi
4. Restore the backups in newly installed sql server 2005.
5. dbcc updateusage with count_rows
6. sp_updatestats
7. rebuild all indexes (individually)(COuld you please tell me what to do in this step)
8. DBCC for DATA_PURITY
9. switch to dblevel 90
10. Run scripted logins and jobs in sql server 2005
11. create a new backup
12. perform test by the application team(s)
point 10, put the logins, jobs in after the databases have been successfully restored otherwise they will likely try and reference databases that dont exist
point 7, have a look around for scripts that rebuild all indexes in a given database. There are plenty of scripts on this site
I've always found upgrade advisor a waste of time personally
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply