INF: SQL Server 2000 Upgrade Fails Because Database is Not in a Writable State (277629)

SUMMARY

When you run an upgrade from Microsoft SQL Server 7.0 to Microsoft SQL Server 2000, the upgrade may fail with the following error message:

Setup

In order to begin an upgrade, databases and filegroups must be writable and you must have permission to access the databases. Correct the problem and restart setup.

The Sqlstp.log file located in the \Winnt folder indicates which database is not in a writable state. For example:

11:28:12 Msg 50000, Level 16, State 1, Server PIERRE, Line 20
11:28:12 Database 'db1' must be made writable before it can be upgraded.
11:28:21 In order to begin an upgrade, databases and filegroups must be writable and you must have permission to access the databases. Correct the problem and restart setup.
11:28:21 End Action DialogShowSdUpgrade
11:28:21 End Action ShowDialogs
11:28:21 Action CleanUpInstall:
11:28:21 StatsGenerate returned: 2
11:28:21 StatsGenerate (0xa008327,0x2,0xf0000000,0x600,1033,0,0xc,0x1,0,0,0
11:28:21 StatsGenerate -1,Administrator)
11:28:21 Installation Failed.

MORE INFORMATION

A database is considered not writable if the database is in any of the following status states:

Loading
Pre-recovery
Recovering
Not recovered
Suspect
Offline
Read only
Emergency mode

You can view the state of the database by opening the SQL Server Enterprise Manager and expanding the databases folder. If the database is in any of the preceding states the state condition displays next to the database name in parenthesis.

If the database is in a "recovering" or a "pre-recovery" state, wait and let the database finish recovering, and then restart the upgrade.
If the database is in a "not recovered" or "suspect" state, and you need to attempt to recover the database, please contact Microsoft Product Support Services (PSS).

You must take the appropriate steps to change the database to a writable state before you proceed with the upgrade. A writable state would include a database that does not have any special options set. The following settings, or combination of settings are considered writable and do not pose a problem:

Autoclose
SELECT INTO or bulkcopy
Truncate log on checkpoint
Autoshrink

If the database is not needed and you do not want to upgrade, you can drop the database before you run the SQL Server 2000 upgrade.