Database ConstraintSTD_2016v1

Referential Integrity Enforcement

Ensures foreign key relationships are maintained and no orphan records exist.

Owner: Unassigned

Updated: 10/31/2025

Business Rule

All child records must reference valid parent records. Prevents data inconsistencies.

Technical Implementation

Database foreign key constraints with appropriate CASCADE or RESTRICT rules.

Examples

Good practices vs common violations

Good Examples

Order.CustomerID references valid Customer.ID

Poor Examples (Violations)

Order referencing non-existent CustomerID creating orphan record

Additional Information

Target Industries

All

Status

active

Local Network

DQ Improvements

Data quality dimensions improved by this standard

Coherence

high

The degree to which datasets can be combined.

Type: prevents

Linkability

high

The degree to which records of one data file can be correctly coupled with records of another data file.

Type: prevents

Referential integrity

high

The degree to which data values of the primary key of one data file and data values of the foreign key of another data file are equal.

Type: prevents

Quick Stats

Related KPIs0

DQ Improvements3

Versionv1

API Access

GET /api/standards/referential-integrity-enforcement