%1 (%2) %3Database recovery stopped abruptly while redoing logfile %4 (%5,%6). The logs after this point may not be recognizable and will not be processed. For more information, click http://www.microsoft.com/contentredirect.asp.
Database recovery failed with error %4 because it encountered references to a database, '%5', which is no longer present. ...
Database recovery on '%2' failed with error %1. The database is not in the state expected at the first reference of this ...
Database recovery on '%5' failed with error %4. The database is not in the state expected at the first reference of this ...
Database recovery stopped abruptly while redoing logfile %1 (%2,%3). The logs after this point may not be recognizable and ...
Database recovery stopped abruptly while redoing logfile %4 (%5,%6). The logs after this point may not be recognizable and ...
Database recovery/restore failed with unexpected error %4. For more information, click http://www.microsoft.com/contentredirect.asp. ...
Database RPC Latency Root Cause Responder successfully executed last time and found no issues, turning monitor green so responder ...
Database schema version check monitor for one or more database(s) failed to take appropriate provisioning action. Please ...
Database size monitor for database '{0}' may have failed to take appropriate provisioning action (setting IsExcludedFromProvisioning) ...