What is the best way to produce structured data from a database or SQL system in discovery?
Producing structured data — records held in databases, SQL systems, ERP platforms, or other relational stores — is one of the harder problems in modern discovery. Unlike documents, this data lives in tables, fields, and relationships that have no natural “page” or “file.” The best approach focuses on producing data that is usable, accurate, and proportionate to the needs of the matter.
Start With the Form of Production
Discovery rules generally let the requesting party specify a reasonable form of production, and the producing party may object or propose an alternative. For databases, the practical choices usually include:
- Structured exports (delimited files such as CSV, or database dumps) that preserve fields, data types, and relationships.
- Reports or queries that answer specific questions rather than dumping an entire system.
- Targeted extracts limited to the relevant tables, date ranges, and custodians.
Producing a static report (for example, a PDF screen capture) is often the least useful form, because it strips out the underlying field structure and makes the data difficult to analyze.
Negotiate Scope and Format Early
The single most effective practice is to confer early about what the data means and how it should be produced. The parties should discuss the data dictionary or schema, which fields are relevant, how codes and lookup values translate, and whether full database access is necessary or whether a defined query will suffice. This avoids over-collection, protects privacy, and reduces cost — all consistent with proportionality.
Preserve Integrity and Document the Process
Capture and document the extraction method, the query logic used, and any transformations applied so the output is defensible and reproducible. Maintaining accuracy and a clear chain of how data was pulled supports authenticity if the production is later challenged. Where the data contains personal or sensitive information, apply appropriate privacy controls and consider redaction or field-level masking.
Remember that the specific rules, forms, and timing differ by jurisdiction — federal courts, state courts, and other countries each set their own standards. Confirm what applies to your matter.
For related concepts, see e-discovery topics.
Sources & further reading
Authoritative government and non-profit references.
- Federal Rules of Civil Procedure — U.S. Courts
- The Sedona Conference publications — The Sedona Conference
How to cite this page
APA
RM University Editorial. (2026). What is the best way to produce structured data from a database or SQL system in discovery?. Records Management University. https://www.recordsmgmt.org/questions/producing-structured-data-databases-discovery/
MLA
RM University Editorial. "What is the best way to produce structured data from a database or SQL system in discovery?." Records Management University, 16 June 2026, www.recordsmgmt.org/questions/producing-structured-data-databases-discovery/.
Related questions
- A key custodian left the company—how do we preserve and collect their email and files after they're gone?
- An employee admitted to deleting emails relevant to a lawsuit—what do we do now?
- Are curative measures or monetary fines available when lost data can be replaced through other sources?
- Can a company be sanctioned for spoliation when an employee auto-deleted text messages or ephemeral chats?
- Can a court order cost-shifting or limit search terms when keyword searches return an unmanageable hit count?