Symptoms: Status of the SQL database is not ONLINE
Impact: Critical
The database is unavailable.
Expected behavior :
Any instance where the status is not ONLINE needs to be investigated.
Possible causes
Database corruption Priority: Critical
When SQL Server starts up, it will try to run recovery on any corrupted database. Where this fails, it will put the database into the SUSPECT state.
Recommended action :
We suggest that the correct procedure is to restore from backups. If there are no backups available, possibly try to get the database into EMERGENCY mode and extract as much data as possible, or run EMERGENCY-mode repair.
Database recovering or restoring Priority: High
Recommended action :
Monitor the recovery or restore process to ensure that it is completed.
User action Priority: High
Recommended action :
Refer to the user who initiated this change
Background
A database is always in one specific state.
EMERGENCY: A user has changed the database and set this status. The database is in single-user mode and may be repaired or restored. The database is marked READ_ONLY, logging is disabled, and access is limited to members of the sysadmin fixed server role.
SUSPECT: At least the primary filegroup is suspect and may be damaged. The database cannot be recovered during the startup of the SQL Server. The database is unavailable. Additional action by the user is required to resolve the problem.
OFFLINE: Database is unavailable. A database becomes offline by explicit user action and remains offline until an additional user action is taken.
RESTORING: One or more files of the primary filegroup are being restored, or one or more secondary files are being restored offline. The database is unavailable.
RECOVERING: Database is being recovered. The recovering process is a transient state; the database will automatically become online if the recovery succeeds. If the recovery fails, the database will become suspect. The database is unavailable.
RECOVERY PENDING: SQL Server has encountered a resource-related error during recovery. The database is not damaged, but files may be missing or system resource limitations may be preventing it from starting. The database is unavailable. Additional action by the user is required to resolve the error and let the recovery process be completed.
