Inspect LastGoodCheckDbTime for each database, flag stale or unavailable checks, and compare metadata with retained integrity-job evidence.
Find Damaged Pages in SQL Server With suspect_pages
Find damaged pages in SQL Server by reading msdb.dbo.suspect_pages. Decode the event type, find the table behind each page and know what to do next.
Device Is Not Ready: Fix Operating System Error 21
Device Is Not Ready is the Windows text behind operating system error 21, which SQL Server reports inside error 823. This post explains what the message means, lists the common causes, and gives read-only checks to run before any restart. It ends with the DBCC CHECKDB step that proves the database is healthy.
Running DBCC CHECKDB on a Restored Copy Instead of Production
Run CHECKDB on a restored copy to validate a recoverable backup, retain the full check output, and understand what remains untested.
SQL SERVER – How to DROP or DELETE Suspect Database?
A client’s production database was stuck in suspect state and they could not even drop it. Here is how I helped them drop the suspect database.
What Part of the SQLDump Suggest Database Corruption? – Interview Question of the Week #188
What part of the SQLDump suggest database corruption? A reader asked, and I show the DbccResults tag in the SQLDump text file that confirms it.
Splitting DBCC CHECKDB Across the Week for a Large Database
Keep a large database under regular integrity checks by splitting DBCC CHECKDB work across seven nights and auditing coverage.