May 13, 2004 at 10:19 am
My NT administrator is performing an in-line upgrade from NT 4.0 to Win2K. I was then going to shutdown SQL Server 7.0 and perform an un-install. This should leave my database datafiles on the server. I thought I could then install SQL Server 2000 and then issue a sp_attach_db to attach the 7.0 database into 2000. Has anyone done this successfully and if so, was there any other issues that came about sometime afterwards? I know another option would be to restore the 7.0 backup into 2000.
Thank you.
May 13, 2004 at 11:02 am
All but the system databases (master, msdb, distribution, and model (model may be fine but I don't recall for sure)) can be done that way. I have done the upgrade myself as an upgrade and had no issues. Just make sure you backup your database beforehand for safety.
May 13, 2004 at 11:50 am
You shouldn't have a problem attaching a SQL 7 user DB in SQL 2K. I don't think you can go back after you've done this though. As Antares686 suggests, back it up first!
May 13, 2004 at 12:42 pm
Wouldn't the logins be lost in this process?
May 13, 2004 at 2:02 pm
Don't your company has spare server? I don't like playing the way your NT Admin is function because you could risk losing data, corupting database and no backups. I haven't seen any plan to backup any database before you uninstall at all. I have move sql 7 from nt 4 to window 2000 before, it's not that bad. It should not take you more then 2 hr to get everything up on the 2000 server.
mom
May 13, 2004 at 2:43 pm
Thank you to all those that have responded. I am using scripts to capture logins, database users, and database user permissions into flat files. The user database will be backed up prior to work commencing and the backup will be moved to a different server for safe keeping along with the flat files. Therefore, I will shutdown SQL Server 7.0, I will then uninstall SQL Server 7.0, I will then install SQL Server 2000 Standard Edition with SP3a, I will then run the script to rebuild the logins, and then attach the user database, which the database files should still be intact because the uninstall and install will not delete them. Since the database users and permissions are kept within the user database system tables, once the database is attached the users and permissions will be intact. But, I have them scripted to a flat file if I need to reapply them.
May 13, 2004 at 3:31 pm
If you are going to install SQL 2K on a system that has had SQL 7 installed you might as well use the upgrade method (IMHO). If you are hoping to cleanup the system a bit I suggest reinstall the OS clean, patch, then install SQL 2k and patch.
May 17, 2004 at 6:36 am
I have done this a few times but just a little differently. Using a spare server (usually a generation newer), install newest version of operating system and sp then install SQL Server on that with newest sp.... create new logins, backup restore new dbs.... test.... at cutover time... backupdbs, copy to new server... shutdown old, rename other one to old servername... run the sp_drop/add server restore dbs into server and you are up and running..
The nice thing about this is you have a complete fallback should anything go wrong... power off this one and power up old server...
The positives, fallback system intact.... newer hardware with latest service packs.... updated operating system and SQL Server.... clean hard drive....
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply