Forced database
recovery differs from normal database recovery.
- Forced
recovery marks all storage within the database as in use – In order to
recover a potentially inconsistent allocation map, all storage within
the database is marked as in use. Use the sp_iqcheckdb in dropleaks mode
to reset the allocation map to the correct state.
- Incremental backups are disabled – After the database
is opened in forced recovery mode, incremental backups are disabled.
The next backup must be a full backup. Doing a full backup reenables
incremental backups.
- The forced recovery parameter applies to all opens
of the database while the server is up – Therefore, after the database
is opened, the DBA needs to bring the server back down, and then
restart the server without the forced recovery flag, to be sure
that subsequent opens run in regular mode. Repeated opens of the
database with forced recovery on do not harm the database, but could
be confusing to the DBA. Each time you open the database in forced
recovery mode, all the storage within the database is marked as
in use.