jhuangc
asked on
Upgrade SQL7.0 to SQL7.0 on another machine
We bought a new machine and want to move the SQL7.0 databases on old machine to new powerful machine.
--
The SQL7.0 setup on old machine as followed: DRIVE C: has SQL programs and DRIVE D: has all databases including all system databases.
The SQL7.0 has been installed on new machine as followed;
DRIVE C: has SQL programs ,
DRIVE D: used for other applications, drive E: will host log files only
Drive F: will host data files and all such system databases as master, msdb, model and tempdb.
--
I am able to backup user databases and using RESTORE DATABASE WITH MOVE option to place all user databases to the right locations which is DRIVE F: has data files and E: has log files. BUT for system database master, tempdb, msdb and model database, I am not sure how to do it.
***
One of my friends told me that i can use ALTER DATABASE tempdb MODIFY FILE to do it to relcate the tempdb only.
For msddb database, We tried backup the database and RESTORE DATABASE WITH MOVE OPTION and it works.
I tried to use the same way to move model database or tempdb and always got warning message such as .. can't drop the database because it is a system database.
After a couple of hours trying, I ended up directly edit two systems tables(sysdatabases and sysdevices) in the master databases on the new machine.
---
My new machine is up and running but we have not tested the whole databases yet. Are there any other system tables which i need to edit too? or any other suggestion to deal with my situation with system tables.
p.s.: The way I move over master databas is backing up the master file on old machine then restored back to new machine by using "sqlservr -m" and "osql" to bring up the SQL server normally.
--
The SQL7.0 setup on old machine as followed: DRIVE C: has SQL programs and DRIVE D: has all databases including all system databases.
The SQL7.0 has been installed on new machine as followed;
DRIVE C: has SQL programs ,
DRIVE D: used for other applications, drive E: will host log files only
Drive F: will host data files and all such system databases as master, msdb, model and tempdb.
--
I am able to backup user databases and using RESTORE DATABASE WITH MOVE option to place all user databases to the right locations which is DRIVE F: has data files and E: has log files. BUT for system database master, tempdb, msdb and model database, I am not sure how to do it.
***
One of my friends told me that i can use ALTER DATABASE tempdb MODIFY FILE to do it to relcate the tempdb only.
For msddb database, We tried backup the database and RESTORE DATABASE WITH MOVE OPTION and it works.
I tried to use the same way to move model database or tempdb and always got warning message such as .. can't drop the database because it is a system database.
After a couple of hours trying, I ended up directly edit two systems tables(sysdatabases and sysdevices) in the master databases on the new machine.
---
My new machine is up and running but we have not tested the whole databases yet. Are there any other system tables which i need to edit too? or any other suggestion to deal with my situation with system tables.
p.s.: The way I move over master databas is backing up the master file on old machine then restored back to new machine by using "sqlservr -m" and "osql" to bring up the SQL server normally.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
After reading through the article of the microsoft resolution, I think if you look into two tables(sysdatabases and sysdevices) in the new master database, you will find out the file location of the master is still written as "Drive D:". My concerns is will the entries using "Drive d:" instead of "Drive e:" in sysdatabases and sysdevices tables afffect something in the long run even though SQL runs at this moment. Do I need to go ahead edit the entries in sysdatabases and sysdevices to "Drive E:".
Thansk,
Jimmy
Thansk,
Jimmy
ASKER