Troubleshooting

This section explains some ways to correct problems you may have encountered when upgrading SQL Server.

If you encounter a problem after copying all the files, remove all SQL directories and files and remove any entries in the Registry for SQL Server. Be careful when editing anything in the Registry. Should you inadvertently delete a key that does not belong to SQL Server, you can restore the Registry with the backup you made earlier. For information about restoring the Registry, see the documentation included with Microsoft SQL Server.

Caution Using the Registry Editor incorrectly can cause serious problems that require you to reinstall SQL Server. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

If you are upgrading from SQL Server 4.2x, remove \SQLServer and \SQLMonitor from the following:

\HKEY_LOCAL_MACHINE

\SOFTWARE

\Microsoft

\SQLServer

\HKEY_LOCAL_MACHINE

\SYSTEM

\CurrentControlSet

\Services

\SQLServer

\HKEY_LOCAL_MACHINE

\SYSTEM

\CurrentControlSet

\Services

\SQLMonitor

If you are upgrading from SQL Server 6.0, remove \MSSQLServer and \SQL Executive from the following:

\HKEY_LOCAL_MACHINE

\SOFTWARE

\Microsoft

\MSSQLServer

\HKEY_LOCAL_MACHINE

\SYSTEM

\CurrentControlSet

\Services

\MSSQLServer

\HKEY_LOCAL_MACHINE

\SYSTEM

\CurrentControlSet

\Services

\SQL Executive

After the preceding entries are removed, you have two options to try the upgrade again:

Option One
Reinstall the original SQL Server version.

Once installed, stop the SQL Server services and replace all of the data and log device files, including Master.dat, with the backed-up versions. The directories for these files are listed in the phyname column of the output from the sysdevices table. You noted the file names in the "Microsoft Windows NT Backup" section earlier.

Fix whatever caused the upgrade to fail and try the upgrade again. If the upgrade does not successfully complete, contact your primary support provider.
Option Two
Reinstall the SQL Server version that you are trying to upgrade to.

Re-execute the CREATE DATABASE statement and the ALTER DATABASE statement to re-establish the fragments.
- The user databases need to be re-created in exactly the same way that they were originally created. That is, the device usage, log space allocation, and segment definitions in the new database must have values identical to those that existed when the database was dumped. This information is kept in the sysusages table of the master database. You can also find this information in the output from the Sqldump.sql script that you ran in the "Microsoft SQL Server Dump" section earlier.
  Load the earlier version of the SQL Server databases, while keeping the following in mind:
- The user database dump must be a full database dump, not a transaction log dump.
- The SQL Server version that you are trying to upgrade to must use the same sort order as the earlier version.

Note The master database is not allowed to be loaded or upgraded from earlier versions of SQL Server dumps.