October 3, 2003 at 1:29 pm
Hi,
I was wondering if anyone has come across this error when performing an upgrade from SQL 7.0 to SQL 2000. When I run the upgrade to SQL 2000 I get the following error, "error running script:
upgrade.sql (1)".
The O/S is NT 4 sp6.
After reviewing the event viewer the problem appears to point to procedure:
sp_msupg_upgradecatalog detected inconsistent versioning!
We use Full Text catalogs in our DB's.
Any pointer's would be appreciated.
October 5, 2003 at 5:40 pm
You may have a look at http://support.microsoft.com/default.aspx?scid=kb;EN-US;300676
October 6, 2003 at 7:08 am
Thanks for your help, the article was very helpful.
The article points to a script called "Messages.sql". The erroring displayed in my case is "upgrade.sql". In your opinion would you pursue trying this fix based on the differences "Messages.sql" vrs "Upgrade.sql".
I'm trying to decide is it best to restore sql7 and try the upgrade again or give the fix a chance even though the difference "Messages.sql" and "Upgrade.sql" may be a different issue.
What do you think?
Thanks again
October 6, 2003 at 7:16 am
Hi 01569,
quote:
I was wondering if anyone has come across this error when performing an upgrade from SQL 7.0 to SQL 2000. When I run the upgrade to SQL 2000 I get the following error, "error running script:upgrade.sql (1)".
The O/S is NT 4 sp6.
After reviewing the event viewer the problem appears to point to procedure:
sp_msupg_upgradecatalog detected inconsistent versioning!
We use Full Text catalogs in our DB's.
not sure if this will help you, but here it goes.
When I take one of my db's home (NT4 sp6, sql7, full text catalog) I simply sp_detach it, burn mdf and ldf on CD (not the catalog directory), copy at home and sp_attach it to SQL2K on WIn2K sp3(?). I have a script to built full text catalog again which I run after attaching. I'm doing this frequently and this works just fine.
HTH
Frank
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]
October 6, 2003 at 8:18 am
I think I'll try the fix mentioned in article 300676 even though the error I've recv'd specifies "Update.sql" and NOT "Messages.sql". If my results are still the same (failed). I'll un-install whatever exists of sql2K and rebuild SQL7. Delete all catalogs that exist in the DB's. Then perform the upgrade to SQL2K. If successful rebuild the deleted catalogs. I believe the catalogs somehow are the problem where the error message identified in the NT event viewer relates to "sp_msupg_upgradecatalog".
Maybe I'll get lucky with the article fix.
Thanks again
October 15, 2003 at 11:49 am
Ended up restoring sql7, removed the application databases with the objective to upgrade only the system DB's resulting in the same error.
My Solution: Removing SQL 7.0, Installing sql 2K w/sp3a. Attached the application DB's or DB restore. And dealt with the orphans, jobs Packages etc separately...
Pretty difficult upgrade for something that's supposed to be a snap. Maybe the next one will go better.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply