The remote copy of database "*" is not recovered far enough to enable database mirroring or to join *
Database "*" requires database logs to be restored either on the future mirror database before you c*
The remote copy of database "*" has not had enough log backups applied to roll forward all of its fi*
Database "*" might contain bulk logged changes that have not been backed up. Take a log backup on th*
The mirror database, "*", has insufficient transaction log data to preserve the log backup chain of *
The remote copy of database "*" has not been restored to a log backup that includes all filestream d*
File '*' cannot be reused until after the next BACKUP LOG operation. If the database is participatin*
The SQL statement cannot be executed because filegroup '*' is offline. Use the sys.database_files or*
The device '*' does not exist. Use sys.backup_devices to show available devices.*
The page *, object ID *, index ID *, partition ID *, allocation unit ID * (type *) has been modified*
Repair has invalidated the differential bitmap for database *. The differential backup chain is brok*
Bulk-logging has been turned on for database *. To ensure that all data has been secured, run backup*
Cannot BACKUP or RESTORE a database snapshot.*
The primary filegroup cannot be backed up as a file backup because the database is using the SIMPLE *
The differential backup is not allowed because it would be based on more than one base backup. Multi*
The backup of the file or filegroup "*" is not permitted because it is not online. Container state: *
The specified device type is not supported for backup mirroring.*
Could not insert a backup or restore history/detail record in the msdb database. This may indicate a*
Invalid backup mirror specification. All mirrors must have the same number of members.*
All backup devices must be of the same general class (for example, DISK and TAPE).*
Backup of file '*' is not permitted because it contains pages subject to an online restore sequence.*
Cannot perform a backup or restore operation within a transaction.*
Backup, file manipulation operations (such as ALTER DATABASE ADD FILE) and encryption changes on a d*
You can only perform a full backup of the master database. Use BACKUP DATABASE to back up the entire*
BACKUP DATABASE cannot be used on a database opened in emergency mode.*
Cannot perform a differential backup for database "*", because a current database backup does not ex*
The file name "*" is invalid as a backup device name. Reissue the BACKUP statement with a valid file*
Cannot perform a differential backup for file '*' because a current file backup does not exist. Reis*
BACKUP failed to complete the command *. Check the backup application log for detailed messages.*
BACKUP '*' detected an error on page (*:*) in file '*'.*
Invalid zero-length device name. Reissue the BACKUP statement with a valid device name.*
BACKUP or RESTORE requires the NTFS file system for FILESTREAM and full-text support. The path "*" i*
Inconsistent metadata has been encountered. The only possible backup operation is a tail-log backup *
The BackupDirectory registry key is not configured correctly. This key should specify the root path *
BACKUP detected corruption in the database log. Check the errorlog for more information.*
SQL Server could not send the differential information for database file '*' of database '*\\*' to t*
BACKUP LOG was unable to maintain mirroring consistency for database '*'. Database mirroring has bee*
BACKUP LOG was unable to log updates for for database '*'. Subsequent log backups will be required t*
BACKUP '*' detected an error on a page in file '*'.*
Differential file backups can include only read-only data for databases using the simple recovery mo*
Backup destination "*" supports a FILESTREAM filegroup. This filegroup cannot be used as a backup de*
The backup operation has detected an unexpected file in a FILESTREAM container. The backup operation*
Invalid device name. The length of the device name provided exceeds supported limit (maximum length *
This BACKUP or RESTORE command is not supported on a database mirror or secondary replica.*
Cannot backup from a HADRON secondary because it is not in Synchronizing or Synchronized state.*
Write to backup block blob device * failed. Device has reached its limit of allowed blocks. *
Write to backup block blob detected out of order write at offset *, last block offset was at *. *
Striping a backup set across multiple devices is not permitted for file snapshot backups.*
The database * is configured for file snapshot point in time restore, log backups are not permitted.*
Backup encryption is incompatible with file snapshot backup if TDE is not enabled on the database.*
Device name '*' is not a valid MOVE target when restoring from a File Snapshot Backup. *
File Snapshot Backup is only permitted with a single backup device and no additonal mirrored devices*
The file name "*" is invalid as a backup device name for the specified device type. Reissue the BACK*
The backup cannot be performed because 'ENCRYPTION' was requested after the media was formatted with*
The Certificate specified for backup encryption has expired.*
The Backup cannot be performed because the existing media set is formatted with an incompatible vers*
The backup cannot be performed because '*' was requested after the media was formatted with an incom*
Backup Encryption options were specified, Backup Encryption support has not been enabled on this ver*
A partial restore sequence cannot be initiated by this command. To initiate a partial restore sequen*
The filegroup "*" is ambiguous. The identity in the backup set does not match the filegroup that is *
The file "*" is ambiguous. The identity in the backup set does not match the file that is currently *
Master can only be restored and fully recovered in a single step using a full database backup. Optio*
The supplied backup is not on the same recovery path as the database, and is ineligible for use for *
The log or differential backup cannot be restored because no files are ready to rollforward.*
The database "*" does not exist. RESTORE can only create a database when restoring either a full bac*
This backup set will not be restored because all data has already been restored to a point beyond th*
The file "*" is on a recovery path that is inconsistent with application of this backup set. RESTORE*
Invalid database name '*' specified for backup or restore operation.*
The database is using the simple recovery model. The data in the backup it is not consistent with th*
The contents of the file "*" are not consistent with a transition into the restore sequence. A resto*
The backup set in file '*' was created by * and cannot be used for this restore operation.*
This differential backup cannot be restored because the database has not been restored to the correc*
The data set on device '*' is not a SQL Server backup set.*
File '*' was not backed up in file * on device '*'. The file cannot be restored from this backup set*
Backup and restore operations are not allowed on database tempdb.*
The backup set holds a backup of a database other than the existing '*' database.*
The RESTORE operation cannot proceed because one or more files have been added or dropped from the d*
The tail of the log for the database "*" has not been backed up. Use BACKUP LOG WITH NORECOVERY to b*
The backup of the system database on the device * cannot be restored because it was created by a dif*
The database was backed up on a server running version *. That version is incompatible with this ser*
The STOPAT clause provided with this RESTORE statement indicates that the tail of the log contains c*
File * is not in the correct state to have this differential backup applied to it.*
This backup cannot be restored using WITH STANDBY because a database upgrade is needed. Reissue the *
The backup set cannot be restored because the database was damaged when the backup occurred. Salvage*
RESTORE detected an error on page (*:*) in database "*" as read from the backup set.*
RESTORE cannot apply this backup set because the database is suspect. Restore a backup set that repa*
The backup set has been damaged. RESTORE will not attempt to apply this backup set.*
RESTORE WITH CHECKSUM cannot be specified because the backup set does not contain checksum informati*
Damage to the backup set was detected.*
Filegroup '*' cannot be restored because it does not exist in the backup set.*
Restore Log operations are not permitted for a Log Backup with FILE_SNAPSHOT if bulk operations were*
Page * cannot be restored from this backup set. RESTORE PAGE can only be used from full backup sets *
RESTORE master WITH SNAPSHOT is not supported. To restore master from a snapshot backup, stop the se*
Cannot open backup device '*'. Operating system error *.*
The backup or restore was aborted.*
Too many backup devices specified for backup or restore; only * are allowed.*
Backup device '*' does not exist. To view existing backup devices, use the sys.backup_devices catalo*
Backup or restore requires at least one backup device. Rerun your statement specifying a backup devi*
Unexpected end of file while reading beginning of backup set. Confirm that the media contains a vali*
Too many backup mirrors are specified. Only * are allowed.*
Use WITH FORMAT to create a new mirrored backup set.*
Backup mirroring is not available in this edition of SQL Server. See Books Online for more details o*
The specified URL points to a Block Blob. Backup and Restore operations on Block Blobs are not suppo*
Backup To URL failed to write status messages to the Windows Event Log.*
The backup media on "*" is part of media family * which has already been processed on "*". Ensure th*
The media loaded on "*" is formatted to support * media families, but * media families are expected *
The volume mounted on "*" does not have the expected backup set identity. The volume may be obsolete*
The Estimate for the Backup size exceeds the maximum allowed file size on the remote endpoint.*
The backup set on device '*' uses a feature of the Microsoft Tape Format not supported by SQL Server*
Backup to mirrored media sets requires all mirrors to append. Provide all members of the set, or ref*
The file on device '*' is not a valid Microsoft Tape Format backup set.*
The volume on device '*' is a continuation volume for the backup set. Remove it and insert the volum*
The data set on device '*' is a SQL Server backup set not compatible with this version of SQL Server*
The backup set on device '*' was terminated while it was being created and is incomplete. RESTORE se*
The volume on the device "*" is not part of the media set that is currently being processed. Ensure *
The login has insufficient authority. Membership of the sysadmin role is required to use VIRTUAL_DEV*
The backup data at the end of "*" is incorrectly formatted. Backup sets on the media might be damage*
Cannot use the backup file '*' because it was originally formatted with sector size * and is now on *
WITH SNAPSHOT can be used only if the backup set was created WITH SNAPSHOT.*
Backups on raw devices are not supported. '*' is a raw device.*
Filemark on device '*' is not aligned. Re-issue the Restore statement with the same blocksize used t*
Backup failed because there is a mismatch in file metadata for file *.*
A Backup device of type URL was specified without a Credential, Backup/Restore operation cannot proc*
Backup to URL received an exception from the remote endpoint. Exception Message: **
A failure occurred while attempting to execute Backup or Restore with a URL device specified. Consul*
An error occurred while Backup/Restore to URL was initializing. Error message: *.*
Use of the URL device type is limited to a single device during Backup and Restore operations.*
Backup To URL error: Exclusive access to the file * could not be obtained.*
The file * exists on the remote endpoint, and WITH FORMAT was not specified. Backup cannot proceed.*
Backup/Restore to URL device error: *.*
BackupToUrl initiated.*
BACKUP LOG is not possible because bulk logged changes exist in the database and one or more filegro*
The statement * is not allowed while the recovery model is SIMPLE. Use BACKUP DATABASE or change the*
Cannot back up the log of the master database. Use BACKUP DATABASE instead.*
BACKUP LOG cannot be performed because there is no current database backup.*
Bulk-logged operations exist in the database. Perform a BACKUP LOG.*
The log in this backup set begins at LSN *, which is too recent to apply to the database. An earlier*
RESTORE PAGE is not allowed from backups taken with earlier versions of SQL Server.*
This log cannot be restored because a gap in the log chain was created. Use more recent data backups*
A previous restore operation was interrupted and did not complete processing on file '*'. Either res*
The file "*" was not fully restored by a database or file restore. The entire file must be successfu*
The log in this backup set terminates at LSN *, which is too early to apply to the database. A more *
The log in this backup set contains bulk-logged changes. Point-in-time recovery was inhibited. The d*
This backup set cannot be applied because it is on a recovery path that is inconsistent with the dat*
The STOPAT clause specifies a point too early to allow this backup set to be restored. Choose a diff*
This log backup contains bulk-logged changes. It cannot be used to stop at an arbitrary point in tim*
The database has been rolled forward to the end of this backup set and beyond the specified point in*
RESTORE PAGE is not allowed with databases that use the simple recovery model or have broken the log*
The online restore to database '*' failed. It may be appropriate to perform an offline restore inste*
The log in this backup set begins at LSN *, which is too recent to apply to the database. This resto*
Backups taken on earlier versions of SQL Server are not supported by fn_dump_dblog.*
RESTORE LOG is not supported from this data backup because file '*' is too old. Use a regular log ba*
Restore cannot take '*' offline because changes exist that require a log backup. Take a log backup a*
The container cannot be set to the offline state because changes exist that require a log backup.  T*
The container can not be dropped because changes exist that require a log backup.  Take a log backup*
One or more files do not match the primary file of the database. If you are attempting to attach a d*
Database error: * page * for database '*' (database ID *) is invalid.  This error cannot be repaired*
Clustered columnstore index '*' column '*' rowgroup id * on table '*' has one or more data values th*
Clustered columnstore index '*' column '*' rowgroup id * on table '*' has one or more data values th*
Access to the FILESTREAM tombstone table for the database '*' cannot be performed at the moment beca*
Failed to pause catalog for backup. Backup was aborted.*
Clustered columnstore index '*' on table '*' has a missing column segment on column id * and rowgrou*
Clustered columnstore index '*' on table '*', column '*' has one or more values out of range for dat*
Clustered columnstore index '*' on table '*' has a missing dictionary on column id * and rowgroup id*
Failed to read the message body while marshaling a message. This message is a symptom of another pro*
An internal Service Broker error occurred (error = 0x%08x). This error indicates a serious problem w*
Database error: Database * has inconsistent metadata. This error cannot be repaired and prevents fur*
The conversation endpoint with conversation handle '*' is in an inconsistent state. Check the SQL Se*
The @sync_type parameter value must be "automatic", "none", "replication support only", "initialize *
The specified @backup_file_name was not created from database '*'.*
The specified @backup_file_name is not a database backup.*
The log shipping primary database *.* has backup threshold of * minutes and has not performed a back*
The specified @backup_file_name was not taken from database '*'.*
The specified @backup_file_name is not a database backup.*
The device '*' does not exist. Use sys.backup_devices to show available devices.*
The type "*" is an unknown backup device type. Use the type "disk" or "tape".*
The add device request was denied. A physical device named "*" already exists. Only one backup devic*
*: File '*' has an incorrect size. It is listed as * MB, but should be * MB. Diagnose and correct di*
DBCC DBRECOVER failed for database ID *. Restore the database from a backup.*
*: Backup device '*' failed to *. Operating system error *.*
*: * failure on backup device '*'. Operating system error *.*
Could not clear '*' bitmap in database '*' because of error *. As a result, the differential or bulk*
The value specified for the @backupdevicetype parameter is not valid. The value must be 'logical', '*
Could not locate backup header information for database '*' in the specified backup device. Specify *
The specified publication does not allow subscriptions to be initialized from a backup. To allow ini*
Snapshot publications cannot use the option to initialize a subscription from a backup. This option *
Cannot enable the option to initialize a subscription from a backup. This is not supported for non-S*
Possible inconsistent state in the distribution database: dist_backup_lsn {*:*:%04lx}, dist_last_lsn*
A generation that was expected to be in *.dbo.MSmerge_genhistory could not be found. If this error o*
The transactions required for synchronizing the nosync subscription created from the specified backu*
Cannot create the subscription. If you specify a value of "initialize with backup" for the @sync_typ*
Cannot create the subscription. You must specify a value of "Active" or "Subscribed" for the @status*
An unexpected error with HRESULT 0x* occurred while processing backup files. Refer to the SQL Server*
The number of matching backup files (*) is less than the required number (*). Copy all the right bac*
The number of backup files (*) is greater than the available number of bricks (*). You must restore *
No matching backup files were found by any of the bricks. Copy the backup files to the correct backu*
Brick ID * has no backup files available. Copy the backup file for the segment to this brick, and re*
Restore failed because all the backup files did not come from the same backup operation. Retry the r*
Device name '*' is not valid in a Matrix Backup/Restore command. The device name contains illegal ch*
Restore failed because the brick count of * is different from the BACKUP GROUP COUNT * from the back*
An unexpected error occurred while executing a Backup/Restore command. Refer to the SQL Server error*
The backup files of the RESTORE command do not match with the segments of the existing database. Cop*
The backup files of the FULL RESTORE command do not match with the segments of the existing database*
The backup type of all the archive segments is not the same. Copy the correct backup files to the ba*
Fatal error in backup manager*
This command requires a database encryption scan on database '*'. However, the database has changes *
Dropping a credential '*' which could still be used by Managed Backup.*
Warning: Can not check whether the credential '*' is used by managed backup, because *. Please check*
The * operation failed for availability replica '*', because the backup priority value is outside th*
An error occurred while trying to set the initial Backup LSN of database '*'.  Primary database is t*
Synchronization of a secondary database, '*', was interrupted, leaving the database in an inconsiste*
Log backup for database "*" on a secondary replica failed because a synchronization point could not *
Log backup for database "*" on a secondary replica failed because the last backup LSN (0x*) from the*
 Log backup for database "*" on secondary replica failed because the new backup information could no*
RESTORE DATABASE WITH PARTIAL requires the MEMORY_OPTIMIZED_DATA filegroup if the backup contains a *
A BACKUP or RESTORE DATABASE statement that includes the primary filegroup must include the MEMORY_O*
Failed to create a backup file collection snapshot necessary for backup of database '*'. Check the e*
Failed to get checkpoint file information necessary for backup of database '*'. Check the error log *
This command requires a database encryption scan on database '*'. However, the database has changes *
The parameter @state cannot be NULL, and should be 1 or 0. Specify 1 to start SQL Server Managed Bac*
No backup setting is supplied. Please specify at least one backup setting to be configured.*
SQL Server Managed Backup to Windows Azure master switch is not turned on.*
@full_backup_freq_type, @backup_begin_time, @backup_duration, and @log_backup_freq must be specified*
@days_of_week must be specified if @full_backup_freq_type is set to 'Weekly'*
@full_backup_freq_type, @backup_begin_time, @backup_duration, and @log_backup_freq must not be speci*
@days_of_week must not be specified if @full_backup_freq_type is set to 'Daily'*