I/O and consistency errors that can mean damaged pages; diagnose first and restore from backup where possible.
824
SQL Server detected a logical consistency-based I/O errorA page read from disk failed its integrity check: a storage problem that needs a restore.
823
The operating system returned an error during a read or write (I/O error)Windows reported a failed read or write of a database file: a storage problem to fix before restoring.
825
A read of the file succeeded after failing (read-retry warning)A read only succeeded after retrying: an early warning of failing storage that no query reports.
2570
Column value is out of range for its data type (data purity)DBCC found a stored value that is illegal for its data type; DBCC repair cannot fix it, so correct the rows yourself.
601
Could not continue scan with NOLOCK due to data movementA NOLOCK or READ UNCOMMITTED scan lost its place as rows moved; use snapshot isolation instead of dirty reads.
605
Attempt to fetch logical page failed; it belongs to a different allocation unitA page belongs to another allocation unit: corruption at severity 21, a transient NOLOCK read at severity 12.
829
Page is marked RestorePendingA query touched a page whose page restore is not finished; complete the log restore sequence.
8921
Check terminated: a failure was detected while collecting factsDBCC CHECKDB stopped before checking anything, usually for lack of tempdb space or because system tables are damaged.
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
- Backup & Restore 15
- Database State & Recovery 13
- Memory 6
- Query Processing & Performance 7
- High Availability 8
- SQL Server Agent 4
- Linked Servers 7