Databricks enforces primary and foreign key constraints at runtime, so no additional referential integrity checks are required.

Databricks supports defining primary and foreign key constraints in Unity Catalog tables, but they are not enforced by the engine; ACID guarantees apply only to single-table transactions.

Multi-table inserts in Databricks are atomic, so referential integrity is always preserved without extra logic.

Foreign keys in Databricks can only reference hashed identifiers to avoid collisions in parallel writes.