Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
ADOS
Starting Member
5 Posts |
 Posted - 2004-08-13 : 13:40:25
|
| Our SQL Guy is out for a few weeks and I have a machine giving me problems. The current server is a win2k with sql7 on it.The new machine is a win2003 with sql2k on it.I want to move everything that needs to be moved from 7.0 to the new 2k machine. What would be the best way to do this? |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-08-13 : 13:47:04
|
| That will be an upgrade. You can do the upgrade using three different methods:Upgrade wizard - I don't recommend using thissp_detach_db from 7.0/sp_attach_db to 2000BACKUP 7.0/RESTORE 2000I would go with sp_detach_db/sp_attach_db method. Before doing the sp_detach_db, make sure to get a full backup just in case.You would take a full backup when the upgrade is going to be performed, then start your work while all users are disconnected.But I seriously would not upgrade when your SQL Guy is out. Has the application been tested for the 2000 version of SQL Server? There are some things that might not work. This isn't something that you just do. You test it out in a development environment, deploy it to QA for them to test functionality, then do it in a maintenance window while the users are disconnected.Tara |
 |
|
|
ADOS
Starting Member
5 Posts |
Posted - 2004-08-13 : 13:58:39
|
| Yes the application has been tested for 2000.My concern is at the moment that I want to preserve the name of the machine. And by doing this I cannot keep sql7 and sql2k on at the same time. So by doing a detach I can safely move it to a 3rd machine while I unplug the network from old and plug into new and safely move back? |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-08-13 : 14:22:20
|
| and safely move back? Move back to 7.0 after you upgraded to 2000? No, you can't do that. Once in 2000, you can not easily move back to 7.0.Tara |
|
|
|
ADOS
Starting Member
5 Posts |
Posted - 2004-08-13 : 14:46:11
|
| No, what I meant is this.Server 1 (DONKEY) sql7 - detach databaseFTP database to a 3rd serverUnplug server 1 from networkServer 2 (DONKEY) sql2k ftps data from 3rd serverServer 2 atach databaseI want to keep machine name the same. |
|
|
|
Sitka
Aged Yak Warrior
571 Posts |
Posted - 2004-08-13 : 14:56:23
|
This reads real funny, if ADOS did this to me he would either for sure get fired or beaten real badly. But lets suppose there is more to the story.I always like watching Active Directory do it's thing. That is, once the SQL7 functionality of your network has been taken off line. Remove the SQL7 server from the Domain, check that the computer account of that machine has disappeared and that the DNS record is gone. WINS to if you have it. The idea is that your network will have DONKEY totally removed from it(below the UNC level(client map drives, login scripts etc.). Unplug old Donkey. Then plug the new Donkey in and add it as a new server to the domain. quote:
and I have a machine giving me problems
Can you describe these? May the sky and sea shake hands in your soul |
|
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-08-13 : 17:05:58
|
| Yeah, you might want to fix the problems on the machine. I would personally kill you if you did something like this while I was gone. lolMeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
|
|
|
|
|
SQL 7 to SQL 2000