%1 (%2) %3Recovery had to pause (%4 ms) to allow an older read-only transaction to complete. If this condition persists, it can result in stale copies. For more information, click http://www.microsoft.com/contentredirect.asp.
Recovery could only locate up to log file %4 (generation %5) before detecting an out of sequence logs, and could not locate ...
Recovery database '{0}' was created using existing file {1}. The database must be brought into a clean shutdown state before ...
Recovery from the corrupt log condition failed because the local copy for database '%1' could not be recorded as failed. ...
Recovery had to pause (%1 ms) to allow an older read-only transaction to complete. If this condition persists, it can result ...
Recovery had to pause (%4 ms) to allow an older read-only transaction to complete. If this condition persists, it can result ...
Recovery had to pause for a long time (%1 ms) to allow an older read-only transaction to complete. If this condition persists, ...
Recovery had to pause for a long time (%4 ms) to allow an older read-only transaction to complete. If this condition persists, ...
Recovery Sync Commands/sec is the number of Recovery Sync requests that are processed each second. The recovery sync process ...
Recovery Sync Total is the total number of Recovery Sync requests that have been processed since the service was started. ...