Backups and restores that fail on devices, media, versions, log chains or files in use.
3201
Cannot open backup device (operating system error)BACKUP or RESTORE could not open the file; the OS error says why (path, permission, device).
3241
The media family on device is incorrectly formedThe restore file is not a readable backup: not a backup, cut short in transit, or an unreadable format.
3154
The backup set holds a backup of a database other than the existing databaseRESTORE refused to overwrite an existing database that the backup was not taken from.
3159
The tail of the log for the database has not been backed upRestoring over a FULL recovery database would lose changes since the last log backup.
3101
Exclusive access could not be obtained because the database is in useRESTORE needs the database to itself but other sessions are still connected.
3169
The database was backed up on a server running an incompatible versionThe backup comes from a newer SQL Server version and cannot be restored on this one.
4214
BACKUP LOG cannot be performed because there is no current database backupA log backup was attempted before a full backup started the log chain.
3013
BACKUP DATABASE / RESTORE DATABASE is terminating abnormallyThe closing line of every failed BACKUP or RESTORE; the real cause is the error printed just before it.
3117
The log or differential backup cannot be restored because no files are ready to roll forwardA log or differential restore after the database was already recovered (WITH RECOVERY is the default).
3156
File cannot be restored to the location; use WITH MOVERESTORE cannot create a database file at the path stored in the backup; give it a new path with MOVE.
3183
RESTORE detected an error on a page as read from the backup setA page in the backup failed checksum validation during RESTORE: the backup or its source is damaged.
4208
The statement is not allowed while the recovery model is SIMPLEBACKUP LOG on a database in SIMPLE recovery, where log backups do not exist.
4305
The log in this backup set begins at an LSN that is too recent to applyA log backup is missing from the restore sequence; restore the one that contains the LSN named.
1834
The file cannot be overwritten because it is being used by another databaseRESTORE would write a file to a path another attached database uses; restore WITH MOVE to new file names.
3203
Read on the backup device failedThe backup file was opened but could not be read to the end: a truncated copy, a damaged transfer or failing media.
No errors in this category match your search. Search the whole library.
Other categories
- Constraint & Integrity 5
- Logins & Permissions 19
- Connectivity 9
- Syntax & Object Resolution 22
- Data Type & Conversion 15
- Concurrency & Locking 2
- Transactions 5
- Log & Storage Space 3
- Database State & Recovery 13
- Corruption & Consistency 8
- Memory 6
- Query Processing & Performance 7
- High Availability 8
- SQL Server Agent 4
- Linked Servers 7