Database %1!s! has more than %2!s! virtual log files which is excessive. Too many virtual log files can cause long startup and backup times. Consider shrinking the log and using a different growth increment to reduce the number of virtual log files.
Database "%1!s!" is not in the correct state to become the primary database. The log must be restored from the previous primary ...
Database "%1!s!" is read-only on one of the server instances which is incompatible with participating in database mirroring ...
Database "%1!s!" might contain bulk logged changes that have not been backed up. Take a log backup on the principal database ...
Database "%1!s!" requires database logs to be restored either on the future mirror database before you can enable database ...
Database %1!s! has more than %2!s! virtual log files which is excessive. Too many virtual log files can cause long startup ...
Database %1!s! is enabled for Database Mirroring, but has not yet synchronized with its partner. Try the operation again ...
Database %1!s! is enabled for Database Mirroring, but the database lacks quorum: the database cannot be opened. Check the ...
Database %1!s! was shutdown due to error %2!s! in routine '%3!s!'. Restart for non-snapshot databases will be attempted after ...
Database '%1!s!' (database ID %2!s!:%3!s!) was marked for standby or read-only use, but has been modified. The RESTORE LOG ...