SQL Server: Database status Suspect or Recovery Pending

The Suspect or Recovery Pending statuses mean that SQL Server cannot correctly open the database or complete its recovery. In this state, the Torgsoft software does not start or cannot work with data.

Typical situations

• after a sudden power outage,

• after an emergency PC restart,

• when there is not enough free disk space,

• when database files or the disk are damaged.

How it manifests

• the database in SSMS has the Suspect or Recovery Pending status,

• Torgsoft does not start or freezes during startup,

• a message appears saying it is impossible to connect to the database,

• SQL Server does not bring the database to the Online state.

Causes

1. Not enough free disk space
   SQL Server cannot complete transaction log recovery.

2. SQL Server terminated unexpectedly
   The database logical structure was damaged after power loss.

3. Problems accessing database files
   The folder was renamed, access permissions were changed, or antivirus is blocking the files.

4. Physical HDD / SSD issues
   Bad sectors or file system errors.

What to do

Step 1. Check the basics (required)

1. Check the free space on the disk where the database is stored (usually C:\).

•    there should be at least 5–10 GB of free space.

2. Check whether the SQL Server service is running (services.msc).

3. Restart the computer and wait until Windows fully loads.

4. Make sure the database folder has not been moved and is accessible.

Step 2. Try to bring the database out of the emergency state (via SSMS)

 Performed only if SQL Server Management Studio is installed.

1. Connect to the server in SSMS,

2. Switch the database to EMERGENCY mode,

3. Run an integrity check with DBCC CHECKDB.

 In SSMS, run the commands in order (replace TorgsoftDB with your database name):

4. Try to return the database to ONLINE mode.

Result:

• if the database goes to Online — operation is restored,

• if CHECKDB shows unrepairable errors — the database is corrupted.

Step 3. Restore from backup (the most reliable option)

If the database does not leave the Suspect / Recovery Pending status:

1. Find the most recent database archive:

•    locally: C:\DatabaseArchive\

•    or in C:\Torgsoft Log\

•    or in the folder where the archive was saved during the last manual creation

•    or in the cloud (if «Data Security» was enabled).

2. The file has the .mir or .mirz extension.

3. Perform:

•    «Database → Restore from archive» in Torgsoft
  or

•    restore via SSMS.

Verification after completion

• the database has the Online status,

• Torgsoft starts without errors,

• directories, sales, and reports open,

• there are no SQL error messages.

How to prevent recurrence

• use a UPS for the PC that hosts the database,

• ensure automatic archiving (locally or to the cloud),

• constantly monitor database size (SQL Express limit — 10 GB),

• do not allow the system disk to become full,

• periodically check the condition of the HDD / SSD.

Key rule

If the database has the Suspect or Recovery Pending status and does not switch to Online —
restoring from a backup is the only guaranteed way to bring the system back to operation.

What to prepare for technical support

1. A screenshot or the exact database status text in SSMS.

2. Log files:

•    log_server.data

•    server_app_log.data.

3. The date of and availability of the latest archive.

4. The version of Torgsoft and SQL Server.