Database troubleshooting
Database problem stopping work?
The application cannot connect, routine work takes forever, or important records seem to be missing. I investigate the failure without assuming the data needs to be restored or replaced.
Protect the copies you still have
If data may be damaged or missing, avoid deleting files or starting a restore over the current database before checking the backups. A rushed repair can remove the best chance of recovery.
Unavailable does not necessarily mean lost
Full storage, a permissions change, a blocked query or a failed update can make intact data inaccessible. I separate connection and performance problems from possible damage before proposing a change.
- The application cannot connect or times out
- Ordinary tasks suddenly take minutes
- A migration or restore stopped partway through
Database evidence and recovery checks
- Database and application logs, connection settings and permissions
- Storage, connection limits, blocking and long-running queries
- Migration history and recent schema changes
- Available backups, snapshots and restore points before modifying data
Can you guarantee recovery of missing or corrupted data?
No. Recovery depends on what remains and the available copies. Severe corruption may need a specialist recovery provider; I will say when that is the better next step.
What is the application showing you?
Describe what stopped working. You do not need to know the database diagnosis.