The database '{0}' was not mounted because errors occurred either while validating database copies for possible activation, or while attempting to activate another copy. Detailed error(s): {1}
The database %4 created at %5 was not recovered. The recovered database was created at %5. For more information, click h ...
The database %4 has reached its maximum size of %5 MB. If the database cannot be restarted, an offline defragmentation may ...
The database %4 has reached its maximum size of %5 MB. If the database cannot be restarted, an offline defragmentation may ...
The database '{0}' isn't within the current user's management scope. At least one server with a copy of the database must ...
The database '{0}' was not mounted because errors occurred either while validating database copies for possible activation, ...
The database availability group has the same witness server and alternate witness server {0}, but the witness directory is ...
The database availability group member {0} was removed, but cleanup didn't complete. Please verify that the Cluster service ...
The database configuration is invalid and needs to be re-created. Use the Remove-MailboxDatabase cmdlet to remove the existing ...
The database copy '{0}' could not be suspended because the operation is not applicable for a copy that is in Seedingsource ...