Database file was backed up. Database: %1!s!, creation date(time): %2!s!(%3!s!), file list: (%4!s!), pages dumped: %5!s!, number of dump devices: %6!s!, device information: (%7!s!). This is an informational message only. No user action is required.
Database error: %1!s! page %2!s! for database '%3!s!' (database ID %4!s!) is invalid. This error cannot be repaired. You ...
Database error: Database %1!s! has inconsistent metadata. This error cannot be repaired and prevents further DBCC processing. ...
Database file changes were restored. Database: %1!s!, creation date(time): %2!s!(%3!s!), file list: (%4!s!), number of dump ...
Database file differential changes were backed up. Database: %1!s!, creation date(time): %2!s!(%3!s!), file list: (%4!s!), ...
Database file was backed up. Database: %1!s!, creation date(time): %2!s!(%3!s!), file list: (%4!s!), pages dumped: %5!s!, ...
Database file was restored. Database: %1!s!, creation date(time): %2!s!(%3!s!), file list: (%4!s!), number of dump devices: ...
Database ID %1!s!, Page %2!s! is marked RestorePending, which may indicate disk corruption. To recover from this state, perform ...
Database ID %1!s!. Could not mark database as suspect. Getnext NC scan on sys.databases.database_id failed. Refer to previous ...
Database is not fully started up or it is not in an ONLINE state. Try the full-text DDL command again after database is started ...