Validate relationships before loading
Database foreign keys catch some problems, but by then the load may already be halfway through. ETL validation catches relationship errors earlier, routes bad records, and keeps the rest of the workflow under control.
Advanced ETL Processor validates parent-child relationships before writing to the target. That is especially useful when loading files in batches or combining data from several sources.
Common referential checks
- Each order must have an existing customer.
- Each invoice line must match an invoice header.
- Each transaction must map to a valid account.
- Each product movement must reference a known product.
When database constraints are enough
If the load is small and the database already rejects bad relationships clearly, database constraints are often enough. For scheduled, unattended, or multi-file workflows, ETL-side validation gives better diagnostics and fewer half-finished runs.
Useful references
Related pages: lookup validation, data validation types, and PostgreSQL's documentation on constraints.