Database Corruption Repair
Checksum failures, damaged pages or broken indexes after a crash or storage fault. We salvage what is readable and rebuild what is not.
Signs you are here
- Checksum, torn page, or "could not read block" errors
- Queries crash the server on specific tables
- DBCC CHECKDB or amcheck reports damage
- Indexes return wrong or missing rows
Until someone has taken a copy, avoid restarts, repair commands, and restores over the original.
How we approach it
- Image first Copy the damaged files before any repair attempt so nothing gets worse.
- Map the damage Identify exactly which tables, pages and indexes are affected.
- Salvage and rebuild Extract readable data, rebuild indexes, and fill gaps from backups or replicas.
- Prevent a repeat Check storage, settings and monitoring so the fault is caught early next time.
Questions
Should we run the built-in repair tool?
Not before taking a copy. Some repair modes discard data to make the database consistent.
Is this the same as hard-drive recovery?
No. We work on database files that are readable from your systems. Physically failed drives need a data-recovery lab.
Engines we work with
- PostgreSQL
- MySQL
- MariaDB
- SQL Server
- AWS RDS & Aurora
- Google Cloud SQL
- Azure SQL