eG Monitoring
 

Measures reported by MsSqlDbStatusTest

If a user complaints of problems while accessing a database, the knowledge of the current state of that database will enable administrators to promptly diagnose the reason for such an occurrence. This test auto-discovers all the databases on a Microsoft SQL server and reports the current state of each database, thereby enabling administrators to easily troubleshoot issues related to database access.

 The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
Status Indicates the current state of this database. Number The values that this measure can report, the state they represent, and a brief description of the state are provided below:
Value State Description
0 ONLINE Database is available for access. The primary filegroup is online, although the undo phase of recovery may not have been completed.
1 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 in this case.
2 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 in this case.
3 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.
4 SUSPECT At least the primary filegroup is suspect and may be damaged. The database cannot be recovered during startup of SQL Server. The database is unavailable. Additional action by the user is required to resolve the problem.
5 EMERGENCY User has changed the database and set the status to EMERGENCY. 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. EMERGENCY is primarily used for troubleshooting purposes. For example, a database marked as suspect can be set to the EMERGENCY state. This could permit the system administrator read-only access to the database. Only members of the sysadmin fixed server role can set a database to the EMERGENCY state.
6 OFFLINE Database is unavailable. A database becomes offline by explicit user action and remains offline until additional user action is taken. For example, the database may be taken offline in order to move a file to a new disk. The database is then brought back online after the move has been completed.