Re: Moving databases from SQL 7 to SQL 2000 - More Questions!
From: Andrew J. Kelly (sqlmvpnoooospam_at_shadhawk.com)
Date: 02/25/04
- Next message: Randy Hersom: "RE: Detecting MSDE 2000 SP3a and hot fixes"
- Previous message: Joe Erpenbeck: "Reporting Services installs German help"
- In reply to: Andrew Wright: "Moving databases from SQL 7 to SQL 2000 - More Questions!"
- Next in thread: Mateo: "Re: Moving databases from SQL 7 to SQL 2000 - More Questions!"
- Reply: Mateo: "Re: Moving databases from SQL 7 to SQL 2000 - More Questions!"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 25 Feb 2004 09:43:45 -0500
Personally I feel using the copy DB wizard is more effort than just a backup
and restore or simply scripting the objects if you don't want the data.
There is a lot more that can go wrong with the wizard but that doesn't mean
it can't be done either. Here are some links dealing with this issue and
the last one talks about some issues with the wizard:
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465 Using WITH MOVE in a
Restore
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
http://www.support.microsoft.com/?id=274463 Copy DB
Wizard issues
-- Andrew J. Kelly SQL MVP "Andrew Wright" <anonymous@discussions.microsoft.com> wrote in message news:1E8C1DBC-6DF7-4664-A032-FBF97E51336E@microsoft.com... > I know there are numerous threads with similar subjects in this newsgroup but there are a few of questions I need to ask and can't find answers for. > > I am going to copy some SQL 7 databases on an NT 4 server to a Windows 2000 Server running SQL 2000 (both in the same domain). > > Is there a good reason why I shouldn't use the Database Copy Wizard in SQL 2000? I know that is won't copy DTS packages or database diagrams but there are other ways of doing this. > > Is there an advantage to copying the database diagram from the original database or is it just as simple to re-create the diagram in the new database? Do I lose anything by not copying it? > > This last question is a bit of a lame one because I am guessing the answer is 'it will fail with some error', but: > > If I use the copy database wizard and copy a database from SQL 7 on the NT server to SQL 2000 on the Windows 2000 server this will allow me to copy jobs. If some of the jobs I copy want to run DTS packages that I have not yet copied to the new server what happens if the job is run? > > Thanks for any help, > Andrew >
- Next message: Randy Hersom: "RE: Detecting MSDE 2000 SP3a and hot fixes"
- Previous message: Joe Erpenbeck: "Reporting Services installs German help"
- In reply to: Andrew Wright: "Moving databases from SQL 7 to SQL 2000 - More Questions!"
- Next in thread: Mateo: "Re: Moving databases from SQL 7 to SQL 2000 - More Questions!"
- Reply: Mateo: "Re: Moving databases from SQL 7 to SQL 2000 - More Questions!"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
