Restore was successful but deferred transactions remain. These transactions cannot be resolved because there are data that is unavailable. Either use RESTORE to make that data available or drop the filegroups if you never need this data again. Dropping the filegroup results in a defunct filegroup.
RESTORE FILEGROUP="%1!s!" was specified, but not all of its files are present in the backup set. File "%2!s!" is missing. ...
RESTORE LOG is not supported from this data backup because file '%1!s!' is too old. Use a regular log backup to continue ...
RESTORE master WITH SNAPSHOT is not supported. To restore master from a snapshot backup, stop the service and copy the data ...
Restore the mappings of invalid column references by mapping the column references to the columns available in the specified ...
Restore was successful but deferred transactions remain. These transactions cannot be resolved because there are data that ...
RESTORE WITH CONTINUE_AFTER_ERROR was successful but some damage was encountered. Inconsistencies in the database are possible. ...
Restored/synchronized database %{database/} should already exist on target machine and must contain master datasource pointing ...
Resume call failed because the package is not suspended. This occurs when the client calls resume, but the package is not ...
Retain partitions. Partitions for new measure groups will be deployed, but partitions for existing measure groups will be ...