Database "%1!s!" might contain bulk logged changes that have not been backed up. Take a log backup on the principal database or primary database. Then restore this backup either on the mirror database to enable database mirroring or on every secondary database to enable you to join it to the availability group.
Database "%1!s!" is an auto-close database on one of the partnerswhich is incompatible with participating in database mirroring ...
Database "%1!s!" is not in a recovering state which is required for a mirror database or secondary database. The remote database ...
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 ...