August 6, 2007 at 7:27 pm
Hi all,
we are considering to upgrade our SQL server 2000 (enterprise edition) databases , which use simply standard edition's features, to SQL Server 2005 standard edition, side-by-sidy migrating to another box.
I am new to SQL server, basically working on Oracle.
1. Does anyone know whether it is possible? The BOL mentioned it's impossible to cross-version upgrade is not supported. How about migration in our case, considering only standard edition features are using?
2. can model database be migrated by restoring or attaching as user databases? this is because we have some customized templates in SS2K.
Thanks,
Sherry
August 6, 2007 at 11:34 pm
Sherry -
Are you migrating (e.g. starting fresh on a new database server) or upgrading (e.g. running the upgrade process against an existing SQL 2000 instance)?
Joe
August 6, 2007 at 11:38 pm
Joe,
We are migrating (i.e. side-by-side upgrade to a new SQL server box) the databases.
Sherry
August 6, 2007 at 11:54 pm
Sherry -
Your best best is to simply move your databases, logins, jobs, etc. to the new server by backing up/restoring the users databases, scripting logins (or transferring with SSIS), scripting jobs, etc.
You may want to run the upgrade advisor against the SQL 2000 server to make sure that there aren't going to be any gotcha's along the way (e.g. extended store procedures, old style join syntaxes, etc.)
You will not want to bring across MSDB or any of the system databases as they have changed quite a bit in SQL 2005 - you can script your customizations of the SQL 2000 MSDB (e.g. specific tables, etc.) and apply them to the new MSDB but you're not going to be able to just copy the old database onto the new server.
Joe
August 7, 2007 at 12:22 am
Joe,
Thanks for the suggestions.
I agree with you and plan to try with the plan:
1. install SS2K5 on a new box
2. transfer logins from SS2k to SS2k5
3. run UA against the SS2k (I am not sure about this as the SS2k server is under serious condition, frequently reaching 80% - 95% CPU usage).
4. backup SS2k user databases and restore to SS2k5 and change the compatibility level to 90
5. re-create the jobs on SS2k5 as there are simiply maintenance plans for all databases (intergrity check, backup etc.).
6. re-create the full-text catalog on SS2k5 (there is one SS2k database which has full-text catalog). according to BOL, full-text catalog on SS2k is not compatible with that on SS2k5.
7. get developers/key users to test against the migrated databases.
8. cut over.
anything suggestions or if I missed something in the plan?
welcome all input and recommendations.
Thanks,
Sherry
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply