824: SQL Server detected a logical consistency-based I/O error (page corruption)
SQL ServerWhat does it mean?
SQL Server read a page but its content is logically inconsistent (bad checksum, torn page or wrong page ID). The data page is corrupt.
Why does it happen?
Storage subsystem errors, sudden power loss/torn pages, controller or driver problems, silent corruption caught by PAGE_VERIFY CHECKSUM. Like 823, mostly hardware/storage related.
How to fix it
Run DBCC CHECKDB to determine the extent of the corruption. Restore from the last good backup or repair the affected pages with a page-level restore. Examine msdb.dbo.suspect_pages. Make sure PAGE_VERIFY = CHECKSUM is enabled. Inspect the hardware/storage. REPAIR_ALLOW_DATA_LOSS must be the last resort and causes data loss.
More from this engine
- 4060Cannot open database requested by the login. The login failed
- 233A connection was successfully established with the server, but then an error occurred (no process is on the other end of the pipe)
- 823The operating system returned error to SQL Server during a read/write at offset in file (I/O error)
- 701There is insufficient system memory in resource pool to run this query
- 845Time-out occurred while waiting for buffer latch
- 3201Cannot open backup device. Operating system error (backup device error)
- 8134Divide by zero error encountered