Inspect LastGoodCheckDbTime for each database, flag stale or unavailable checks, and compare metadata with retained integrity-job evidence.
SQL SERVER – Quick Look at Suspected Pages
Well, let us take a Quick Look at Suspected Pages which contains details about corrupted pages. They have been running DBCC commands regularly.
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.
SQL SERVER – FIX: Backup Detected Log Corruption in database MyDB. Context is Bad Middle Sector
A client’s full backup always failed at 60%: backup detected log corruption, context is bad middle sector. Here is what the ERRORLOG showed and how we fixed it.