Recovery could not determine the outcome of a cross-database transaction %1!s!, named '%2!s!', in database '%3!s!' (database ID %4!s!). The coordinating database (database ID %5!s!) was unavailable. The transaction was assumed to be committed. If the transaction was not committed, you can retry recovery when the coordinating database is available.
Records when all stored procedures and Transact-SQL batches run. The captured trace provides information about the types ...
Recovering only master database because traceflag 3608 was specified. This is an informational message only. No user action ...
Recovery cannot scan database "%1!s!" for dropped allocation units because an unexpected error has occurred. These allocation ...
Recovery completed for database %1!s! (database ID %2!s!) in %3!s! second(s) (analysis %4!s! ms, redo %5!s! ms, undo %6!s! ...
Recovery could not determine the outcome of a cross-database transaction %1!s!, named '%2!s!', in database '%3!s!' (database ...
Recovery for database '%1!s!' is being skipped because it requires an upgrade but is marked for Standby. Use RESTORE DATABASE ...
Recovery intervals above %1!s! minutes not recommended. Use the RECONFIGURE WITH OVERRIDE statement to force this configuration. ...
Recovery is unable to defer error %1!s!. Errors can only be deferred in databases using the full recovery model and an active ...
Recovery is writing a checkpoint in database '%1!s!' (%2!s!). This is an informational message only. No user action is required. ...