Forced Recovery Mode

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.

• Before Forced Recovery
  Restricting database access provides greater control over inadvertent database opens during forced recovery.
• Starting a Server in Forced Recovery Mode
  Forced recovery allows the server to start if the allocation map is inconsistent.
• Recovering Leaked Space
  Use the sp_iqcheckdb stored procedure in dropleaks mode to recover leaked storage space within the specified database.
• Recovering Multiplex Databases
  Multiplex databases have special recovery requirements.