Re: upgrading from SQL 7.0 to SQL2000
From: Andrew J. Kelly (sqlmvpnoooospam_at_shadhawk.com)
Date: 05/11/04
- Next message: John Kane: "Re: 'Microsoft Search service cannot be administered under the present user error' SP3"
- Previous message: david epsom dot com dot au: "Re: SQL or Access ?"
- In reply to: Don Castiglioni: "Re: upgrading from SQL 7.0 to SQL2000"
- Next in thread: Tibor Karaszi: "Re: upgrading from SQL 7.0 to SQL2000"
- Reply: Tibor Karaszi: "Re: upgrading from SQL 7.0 to SQL2000"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 10 May 2004 20:14:04 -0500
Sounds good except for # 6. I would only use the wizard to transfer things
such as logins and such if you can't easily recreate them. As for the DB's
I would use sp_detach_db and sp_attach_db. It will be much faster and less
likely to have problems. When you attach them they will automatically be
upgraded to 2000. Then you most likely will only have to use
sp_change_users_login to map the logins back to the proper users.
-- Andrew J. Kelly SQL MVP "Don Castiglioni" <don.castiglioni@co.travis.tx.us> wrote in message news:eJCzBnuNEHA.2480@tk2msftngp13.phx.gbl... > Thank you for the help. I like the idea of doing a fresh install of SQL > 2000. After reading the links here is what I think I might do -- if you > think it would work-- > 1) backup all of my SQL 7.0 databases on my production server. > 2) install SQL 7.0 on a separate machine which is a test server. > 3) Restore the databases from my production server on to my test server > running SQL 7.0. Verify that the databases that were restored are > functional. > 4) uninstall SQL 7.0 from my production server. > 5) install a fresh copy of SQL 2000 on my production server and upgrade it > to the latest service pack > 6) use the SQL 2000 copy database wizard to copy all the the SQL 7.0 > databases from the test server (but not the system databases) to my > production server. Then I'm finished, I hope. > Do these steps sound reasonable? > > > "Andrew J. Kelly" <sqlmvpnoooospam@shadhawk.com> wrote in message > news:uiDBm1fNEHA.3712@TK2MSFTNGP10.phx.gbl... > > Personally I prefer to always uninstall the 7.0 and reinstall 2000 when > > ever possible. While the upgrade should work just fine I like to start > > fresh if possible. In either case just make sure you have "TESTED" > backups > > of all your and that you can recreate things such as logins, scheduled > jobs > > etc. If you aren't confident on how to do all of this then maybe an > upgrade > > is best for you. Doing a side by side is the last path I would recommend > > for if nothing else this means you have to make the 2000 a named instance. > > Here are some links that may be of interest: > > > > > > 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 > > > > > > "Don Castiglioni" <don.castiglioni@co.travis.tx.us> wrote in message > > news:eg3UxNfNEHA.1340@TK2MSFTNGP12.phx.gbl... > > > I'm running Microsoft SQL 7.0 enterprise edition version 7.00.961 > running > > on > > > Windows 2000 server service pack 4 build 2195. > > > > > > I'm ready to upgrade to SQL2000. I'm not doing replication or clustering > > and > > > my databases are only 400MB. > > > > > > I have read the Microsoft white paper published September 2000 entitled > > "how > > > to upgrade SQL server 6.5 and 7.02 SQL Server 2000". It seems that I > have > > > the option of either upgrading or installing a second copy of SQL 2000 > > > running alongside my SQL 7.0 and then copying the databases from SQL 7.0 > > to > > > SQL2000. > > > > > > I have an upgrade question. > > > > > > I don't know which option is better, easier, and safer for doing my > > upgrade. > > > > > > should I install a new copy of SQL2000 on the same machine I'm running > SQL > > > 7.0 on, and then copy the databases from SQL 7 to use SQL2000 and then > > > uninstall SQL 7.0? > > > > > > Or should I simply upgrade SQL 7.0 to SQL2000 and let SQL2000 install on > > top > > > of SQL 7.0? > > > > > > Lastly, > > > > > > Is there additional documentation about the upgrade process I should > read? > > > > > > Are there problems I should watch out for when upgrading? > > > > > > > > > > > > > > > > > >
- Next message: John Kane: "Re: 'Microsoft Search service cannot be administered under the present user error' SP3"
- Previous message: david epsom dot com dot au: "Re: SQL or Access ?"
- In reply to: Don Castiglioni: "Re: upgrading from SQL 7.0 to SQL2000"
- Next in thread: Tibor Karaszi: "Re: upgrading from SQL 7.0 to SQL2000"
- Reply: Tibor Karaszi: "Re: upgrading from SQL 7.0 to SQL2000"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
Loading
