Foreign key constraint violation when loading or deleting data in database

Overview

When the destination is a database, and there are multiple source-to-destination transformations in the Flow (for example, when the Flow loads data in multiple database tables), the order in which transformations are executed might matter.

For example, if there are 2 tables linked by the foreign constraint, you will need to load the data into one table before loading it into another. Otherwise, the target database will generate an exception Foreign key constraint violation.

Process

Solution: disable the parallel option for all transformations and reorder the transformations to ensure that the transformations are executed sequentially and in the right order.