January 28, 2002 at 2:58 pm
What not use a 7.0 Backup, then Restore that to a 2000 DB ?
Why is it no one ever recommends this for a Migration Path ?
January 28, 2002 at 3:51 pm
It works, but you've got time to take the backup, time to do the copy, time to restore the database versus primarily time to do the copy.
K. Brian Kelley
http://www.sqlservercentral.com/columnists/bkelley/
K. Brian Kelley
@kbriankelley
January 28, 2002 at 5:08 pm
It should work, but I'm always a little nrevous about moving between versions with something like this.
Steve Jones
January 28, 2002 at 5:29 pm
Thanks guys. This is an awesome site. I have informed all my fellow DBA's about this.
SO, in a situation where the SQL Servers can be taken down for a weekend, what way would you suggest ?
January 29, 2002 at 11:30 am
I'd do the backup if you don't have the time.
If you do, try the detach, attach
Steve Jones
January 29, 2002 at 9:22 pm
Steve ->
We do have a whole weekend where the Servers can be down for this Migration.
Would you suggest using Copy Database Wizard or a Manual Detach, Attach ?
-----------
If Manual :
wouldn't it be better for us to shut down the Servers, then Copy over the files, then Attach. Thus, avoiding the Detach. If so, should we attach System databases first - Master, MSDB, etc...then the User databases ?
(I am wondering about Login Issues.)
January 30, 2002 at 9:53 am
I've had some issues with the Copy Database Wizard, so I tend to not trust as much, ubt when it works it is slick.
You can shut down the server and copy the files. The detach doesn't matter, you can easily attach the files on both servers.
If you are going to copy the files, you will want to do the master and msdb first, then the user databases. This should handle logins and users. If anything is out of synch, sp_change_users_login will fix this. Keep in mind that the server name is stored in master..sysservers. If the new server has a new name, then you will need to sp_dropserver, sp_addserver <name>, Local to correct this.
hope this helps.
Steve Jones
January 31, 2002 at 12:56 pm
That brings up 2 points :
1. If the Server Name is different, do I restore Master, then rename the Server ???
2. Can there be two SQL Servers with the same name on the same Lan Segment ?
(This may be the case when we do the Migration.)
January 31, 2002 at 12:58 pm
IGNORE THE PREVIOUS POST PLEASE :
That brings up 2 points :
1. If the Server Name is different, do I ATTACH Master, then rename the Server ???
2. Can there be two SQL Servers with the same name on the same Lan Segment ?
(This may be the case when we do the Migration.)
January 31, 2002 at 1:59 pm
January 31, 2002 at 2:44 pm
You can't have to servers (windows) with the same names, so hence unless your using named instances of Sql,(2 part name) you can not have 2 Sql servers with the same name, on the same network.
Tom Goltl
January 31, 2002 at 3:11 pm
will Master Attach to a Different Server Name ?
January 31, 2002 at 3:33 pm
January 31, 2002 at 3:55 pm
Our Current SQL Server 7.0 Production box is called SQL1. We are purchasing a New Box soon for SQL Server 2000 Enterprise Edition. I want this to be called SQL1 also.
How do I do this ? (details please)
January 31, 2002 at 7:42 pm
Are you operating in a workgroup, domain, more complex domain model (master, multiple master, full trust), or AD?
K. Brian Kelley
http://www.sqlservercentral.com/columnists/bkelley/
K. Brian Kelley
@kbriankelley
Viewing 15 posts - 1 through 15 (of 25 total)
You must be logged in to reply to this topic. Login to reply