Use-case recommendation

Best Format for Bulk Table Import Testing

CSV is the best default for bulk table import testing when the pipeline is fundamentally tabular and spreadsheet-compatible.

Recommendation

Recommendation

CSV

CSV exposes delimiter, quoting, row-count, and chunking behavior directly in tabular import workflows.

text/csv

SQL

Use SQL when replay order, transactions, or schema-aware seed setup matters.

Files: 14

JSON

Use JSON when nested fields or schema-drift testing are part of the workload.

Files: 22

Related decisions

Related Decisions

FAQ

FAQ

What is the default format recommendation for this use case?

CSV is the recommended default format here.

How should teams validate this recommendation?

Use sample files and manifest endpoints to test compatibility and behavior before rollout.