Recovery situations
Healthy data, unavailable application
Identify the engine and extract schema and records without depending on the discontinued client.
Damaged storage or database
Work from immutable copies, distinguish index/metadata damage from missing record pages and report uncertainty.
Unknown format
Use signatures, companion files, executable dependencies and known values to establish the database family.
Service workflow
- Preserve source media and complete file sets; hash originals.
- Identify engine, version, companion files and application context.
- Assess damage on disposable copies using read-only methods first.
- Extract schema, records, relationships, memo/blob data and deletion state.
- Resolve code pages, dates, numeric precision and application-specific codes.
- Reconcile counts, totals and representative records with business knowledge.
- Deliver data with a transformation and limitation report.
Choosing the output
CSV is useful for transparent archival review but loses types and relationships. SQL staging preserves structure better. A compatible database copy may support the original application, while a new operational system requires explicit migration and behavior validation.
Unknown formats start with database identification. Access files have specific concerns covered by MDB recovery; BDE-managed estates use BDE migration. Application semantics may require executable analysis. See the database pillar for wider choices.
Provide
Original media or verified copies, all companion files, application/installer, known record examples, prior recovery attempts and the required output/use.