BACKUP WITH CONTINUE_AFTER_ERROR successfully generated a backup of the damaged database. Refer to the SQL Server error log for information about the errors that were encountered.
BACKUP LOG is not possible because bulk logged changes exist in the database and one or more filegroups are unavailable. ...
Backup mirroring is not available in this edition of SQL Server. See Books Online for more details on feature support in ...
Backup of file '%1!s!' is not permitted because it contains pages subject to an online restore sequence. Complete the restore ...
Backup to mirrored media sets requires all mirrors to append. Provide all members of the set, or reformat a new media set. ...
BACKUP WITH CONTINUE_AFTER_ERROR successfully generated a backup of the damaged database. Refer to the SQL Server error log ...
Backup, file manipulation operations (such as ALTER DATABASE ADD FILE) and encryption changes on a database must be serialized. ...
Bad input case encountered with multiple consecutive sequence node occurrences while processing data for mining model, %{modelname/}. ...
Bad input case encountered. Sequence node data is not found where expected in the input case while processing data for mining ...
Based on article settings, table %1!s! should have an identity column, but it does not have one. Verify article settings ...