A reader had too many dumps with CPerIndexMetaQS::ErrorAbort. Here is how we traced them to index corruption and the steps we took to fix it.
SQL SERVER – Msg 0, Level 11 – A Severe Error Occurred on the Current Command. The results, if Any, Should be Discarded
Msg 0, Level 11 says a severe error occurred but gives no clue how to fix it. Here is my checklist, starting with DBCC CHECKDB on the database and table.
SQL SERVER – 5 Don’ts When Database Corruption is Detected
Here is an email I received about database corruption and that has lead me to write this quick blog post about database corruption.
SQL SERVER – Running CHECKDB with Minimum Repair Level
CHECKDB found 39 consistency errors and said repair_allow_data_loss is the Minimum Repair Level, but the reader could not finish the repair. Here is my reply.
SQL Agent Alerts for Severity 17 to 25 and Errors 823, 824, 825
Configure Agent alerts for serious severities and errors 823, 824 and 825, connect an operator to Database Mail, and test response delays.
Page Verify CHECKSUM and Why It Matters
Page verify CHECKSUM detects altered database pages on read; inspect old settings, understand new writes, and review suspect pages.
BACKUP WITH CHECKSUM: What It Checks and What It Cannot
Use WITH CHECKSUM for backups, inspect checksum history, verify backup media, and understand why restored CHECKDB tests are still needed.