Moving databases from SQL 7 to SQL 2000 - More Questions!
From: Andrew Wright (anonymous_at_discussions.microsoft.com)
Date: 02/25/04
- Next message: Joe Erpenbeck: "Reporting Services installs German help"
- Previous message: Jasper Smith: "Re: database connection fail"
- Next in thread: Andrew J. Kelly: "Re: Moving databases from SQL 7 to SQL 2000 - More Questions!"
- Reply: Andrew J. Kelly: "Re: Moving databases from SQL 7 to SQL 2000 - More Questions!"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 25 Feb 2004 05:41:06 -0800
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: Joe Erpenbeck: "Reporting Services installs German help"
- Previous message: Jasper Smith: "Re: database connection fail"
- Next in thread: Andrew J. Kelly: "Re: Moving databases from SQL 7 to SQL 2000 - More Questions!"
- Reply: Andrew J. Kelly: "Re: Moving databases from SQL 7 to SQL 2000 - More Questions!"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
