April 19, 2003 at 7:19 am
I am doing some test upgrades from SQL Server 7 SP3 to SQL Server 2000 SP3. I tried to do a direct upgrade, but this did not give me the new interfaces. When I ran the @@Version, however, the engine had updated. When I did an uninstall and reinstall, I was unable to restore the backups I had made in 7.
I am going to try to use the attach command, but I wanted to see how others had tackled this.
April 19, 2003 at 7:37 am
As in new client tools? Attaching SQL 7 mdf to SQL2K works fine.
Andy
April 19, 2003 at 8:49 am
Not sure what you mean by new client tools. I am going to upgrade client machines, but am only testing server upgrades at the moment.
I have never done an installation that didn't also upgrade the interfaces. Since that only leaves uninstalling 7 and installing 2000, I have to have someone to restore the databases. A 7 backup does not seem to be able to do a 2000 restore.
Am I missing something or doing something wrong?
April 19, 2003 at 9:33 am
Guess Im not sure what interface you mean. Upgrading from SQL7 to 2K is relatively painless, can be done in place. Clients apps will work just the same as long as its a pure upgrade (you don't use a named instance or change the name of the server).
Andy
April 20, 2003 at 10:56 am
Andy,
It could be that I did something wrong in the test, but when I completed the install without doing the uninstall, upon completion the Query Analyzer interface looked like the SQL 7 interface, lacking many of the new elements of the 2000 interface.
When I did the uninstall first, I got the correct 2000 interface, complete with nifty new features, but because 2000 does not restore backups made in 7 (which I did not know nor have I read anywhere) I could not restore the server.
Does this help?
April 20, 2003 at 1:52 pm
Did you select client tools when you did the upgrade? Sure you're running the right exe? Been a while, not sure it removes the old QA.
Andy
April 21, 2003 at 9:26 am
Hi, Ron. Just a quick note to let you know that you can restore SQL 7 backup to a SQL 2K database. We do it daily in our production environment. The biggest diffence we has is that you can not restore incremental backup - without restoreing the full backup as part of the same job. But SQL 2K is much fast doing the restore so it doesn't create a problem for us - yet.
Rita
April 22, 2003 at 12:23 pm
Thanks Rita,
I checked another thread and have found that just because I couldn't restore master doesn't mean the same limitation applies to user databases.
I'll be trying to attach the master and msdb to see if that solves my problem.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply