The index "*" for table "*" (RowsetId *) resides on a filegroup ("*") that cannot be accessed becaus*
Database "*" requires database logs to be restored either on the future mirror database before you c*
Database "*" is not in a recovering state which is required for a mirror database or secondary datab*
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*
Cannot attach a database that was being restored.*
The SQL statement cannot be executed because filegroup '*' is offline. Use the sys.database_files or*
Cannot BACKUP or RESTORE a database snapshot.*
The backup of the file or filegroup "*" is not permitted because it is not online. Container state: *
Could not insert a backup or restore history/detail record in the msdb database. This may indicate a*
Backup of file '*' is not permitted because it contains pages subject to an online restore sequence.*
The restart-checkpoint file '*' is from a previous interrupted RESTORE operation and is inconsistent*
Cannot perform a backup or restore operation within a transaction.*
The database "*" is in warm-standby state (set by executing RESTORE WITH STANDBY) and cannot be back*
BACKUP or RESTORE requires the NTFS file system for FILESTREAM and full-text support. The path "*" i*
The BackupDirectory registry key is not configured correctly. This key should specify the root path *
This BACKUP or RESTORE command is not supported on a database mirror or secondary replica.*
The restart-checkpoint file '*' could not be opened.  Operating system error '*'.  Make the file ava*
The database * is configured for file snapshot point in time restore, log backups are not permitted.*
A partial restore sequence cannot be initiated by this command. To initiate a partial restore sequen*
RESTORE cannot operate on database '*' because it is configured for database mirroring or has joined*
RESTORE cannot restore any more pages into file '*' because the maximum number of pages (*) are alre*
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 *
To restore the master database, the server must be running in single-user mode. For information on s*
Master can only be restored and fully recovered in a single step using a full database backup. Optio*
Page * is a control page which cannot be restored in isolation. To repair this page, the entire file*
Cannot restore any database other than master when the server is in single user mode.*
The database is using the simple recovery model. It is not possible to restore a subset of the read-*
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*
Problems were identified while planning for the RESTORE statement. Previous messages provide details*
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*
File initialization failed. RESTORE cannot continue.*
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 file "*" was not relocated using a relative path during the RESTORE step. A relative location is*
The file '*' of restored database '*' is being left in the defunct state because the database is usi*
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*
Restore to snapshot is not allowed with the master database.*
The database to be restored was named '*'. Reissue the statement using the WITH REPLACE option to ov*
File "*" cannot be restored over the existing "*". Reissue the RESTORE statement using WITH REPLACE *
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.*
This RESTORE statement is invalid in the current context. The 'Recover Data Only' option is only def*
The RESTORE operation cannot proceed because one or more files have been added or dropped from the d*
File '*' cannot be restored to '*'. Use WITH MOVE to identify a valid location for the file.*
The tail of the log for the database "*" has not been backed up. Use BACKUP LOG WITH NORECOVERY to b*
The primary file is unavailable. It must be restored or otherwise made available.*
The transaction log was damaged. All data files must be restored before RESTORE LOG can be attempted*
Database '*' was restored, however an error was encountered while replication was being restored/rem*
RESTORE DATABASE could not drop database '*'. Drop the database and then reissue the RESTORE DATABAS*
RESTORE could not start database '*'.*
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*
File * is defunct and cannot be restored into the online database.*
Filegroup * is defunct and cannot be restored into the online database.*
The STOPAT clause provided with this RESTORE statement indicates that the tail of the log contains c*
The file '*' cannot be moved by this RESTORE operation.*
The system database cannot be moved by RESTORE.*
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*
Filegroup '*' cannot be restored because it does not exist in the backup set.*
Restore cannot continue because file '*' cannot be written. Ensure that all files in the database ar*
Restore Log operations are not permitted for a Log Backup with FILE_SNAPSHOT if bulk operations were*
Page * is beyond the end of the file. Only pages that are in the current range of the file can be re*
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*
RESTORE requires MAXTRANSFERSIZE=* but * was specified.*
The backup or restore was aborted.*
Too many backup devices specified for backup or restore; only * are allowed.*
Backup or restore requires at least one backup device. Rerun your statement specifying a backup devi*
RESTORE REWINDONLY is only applicable to tape devices.*
The specified URL points to a Block Blob. Backup and Restore operations on Block Blobs are not suppo*
Logical file '*' is not part of database '*'. Use RESTORE FILELISTONLY to list the logical file name*
The backup set on device '*' was terminated while it was being created and is incomplete. RESTORE se*
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 restore the file '*' because it was originally written with sector size *; '*' is now on a de*
Filemark on device '*' is not aligned. Re-issue the Restore statement with the same blocksize used t*
A Backup device of type URL was specified without a Credential, Backup/Restore operation cannot proc*
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/Restore to URL device error: *.*
Recovery for database '*' is being skipped because it requires an upgrade but is marked for Standby.*
The option "*" conflicts with online restore. Remove the conflicting option and reissue the command.*
The roll forward start point is now at log sequence number (LSN) *. Additional roll forward past LSN*
The log in this backup set begins at LSN *, which is too recent to apply to the database. An earlier*
The online restore to database '*' failed. It may be appropriate to perform an offline restore inste*
The state of file "*" prevents restoring individual pages.  Only a file restore is currently possibl*
RESTORE PAGE is not allowed on file "*" because the file is not online.*
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*
File '*' has been rolled forward to LSN *. This log terminates at LSN *, which is too early to apply*
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*
A previous RESTORE WITH CONTINUE_AFTER_ERROR operation left the database in a potentially damaged st*
The log in this backup set terminates at LSN *, which is too early to apply to the database. A more *
The file "*" is missing. Roll forward stops at log sequence number *. The file is created at log seq*
This backup set cannot be applied because it is on a recovery path that is inconsistent with the dat*
The database cannot be recovered because the files have been restored to inconsistent points in time*
RESTORE LOG has been halted. To use the database in its current state, run RESTORE DATABASE * WITH R*
The database cannot be recovered because the log was not restored.*
The filegroup "*" has been dropped and cannot be restored into the online database.*
The file "*" has been dropped and cannot be restored into the online database.*
The STOPAT clause specifies a point too early to allow this backup set to be restored. Choose a diff*
The point-in-time clause of this RESTORE statement is restricted for use by RESTORE LOG statements o*
Point-in-time recovery is not possible unless the primary filegroup is part of the restore sequence.*
The database has been rolled forward to the end of this backup set and beyond the specified point in*
RESTORE PAGE is not allowed on read-only databases or filegroups.*
RESTORE PAGE is not allowed with databases that use the simple recovery model or have broken the log*
The current restore sequence was previously interrupted during the transition to the online state. R*
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*
The list of pages provided with the RESTORE PAGE statement is incorrectly formatted. Prior to the pr*
RESTORE LOG is not supported from this data backup because file '*' is too old. Use a regular log ba*
The revert command is incorrectly specified. The RESTORE statement must be of the form: RESTORE DATA*
Restore cannot take '*' offline because changes exist that require a log backup. Take a log backup a*
The database can not be brought online because file '*' is currently restored to LSN * but must be r*
The STOPAT option cannot be used with this partial restore sequence because one or more FILESTREAM f*
RESTORE LOG WITH CONTINUE_AFTER_ERROR was unsuccessful. Execution of the RESTORE command was aborted*
The file '*' cannot be restored to a persistent main memory volume.*
A database or filegroup cannot be set to read-only mode when any files are subject to a RESTORE PAGE*
The recovery model cannot be changed to SIMPLE when any files are subject to a RESTORE PAGE operatio*
The file header in '*' does not match the expected contents for file '*' of database '*'. The mismat*
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*
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*
Query notification cleanup could not access metadata for database "*". Check whether the database is*
The conversation endpoint with conversation handle '*' is in an inconsistent state. Check the SQL Se*
The database for this conversation endpoint is attached or restored.*
The database for the remote conversation endpoint is attached or restored.*
RESTORE WITH SNAPSHOTRESTOREPHASE=2 for database '*' failed because an earlier RESTORE WITH SNAPSHOT*
The log shipping secondary database *.* has restore threshold of * minutes and is out of sync. No re*
*: 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.*
During restore restart, an I/O error occurred on checkpoint file '*' (operating system error *). The*
During a RESTORE operation, an I/O error occurred on checkpoint file '*' (operating system error *).*
Failed to restore the max allocated identity value for article '*' in publication '*'.*
A generation that was expected to be in *.dbo.MSmerge_genhistory could not be found. If this error o*
Snapshot can not process article '*' in publication '*', the clustered index on indexed view '*' may*
Project restore has failed. You cannot restore a project having an object_version_lsn that is the sa*
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 *
Restore recovery failed because a problem was detected with data in a temporary file that is needed *
Restore failed because all the backup files did not come from the same backup operation. Retry the r*
Restore failed because of an internal communications error. Retry the restore operation after addres*
Device name '*' is not valid in a Matrix Backup/Restore command. The device name contains illegal ch*
Restore command is not valid as both Standalone and Matrix archives were found while disambiguating *
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*
Device name '*' is not a valid MOVE target of a Matrix Restore command. Retry the command using a va*
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*
The alert for 'unrestored log' has been raised. The current value of '*' surpasses the threshold '*'*
Database "*" is not in the correct state to become the primary database.  The log must be restored f*
Synchronization of a secondary database, '*', was interrupted, leaving the database in an inconsiste*
A previous RESTORE WITH CONTINUE_AFTER_ERROR operation or being removed while in the SUSPECT state f*
Could not find database '*' at time '*' that can be restored.*
Database 'master' cannot be restored.*
Quota for maximum number of concurrent restores has been exceeded.*
Restore is not enabled on the server.*
Quota for number of restores has been exceeded.*
Could not successfully restore database because the maximum duration for processing a restore has el*
Could not successfully restore database. This request has been assigned a tracing ID of '*'.  Provid*
Restore has been cancelled by a system administrator.*
An internal error was encountered when processing the restore request. This request has been assigne*
Database '*' is currently being restored and cannot be dropped. Please wait for restore to complete.*
Restore operation failed for database '*' with internal error code '0x*'.*
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*
Restore operation failed for database '*' due to insufficient memory in the resource pool '*'. Close*
Federation member database cannot be restored.*