Domain-key normal form

Domain-key normal form (DK/NF or DKNF) is a <a href="/facts/Database_normalization/uLCKbIBz">normal form</a> used in <a href="/facts/Database_normalization/uLCKbIBz">database normalization</a> which requires that the database contains no constraints other than <a href="/facts/Data_domain/4oDqjYsd">domain constraints</a> and key constraints.
A domain constraint specifies the permissible values for a given attribute, while a key constraint specifies the attributes that uniquely identify a row in a given table.
The domain/key normal form is achieved when every constraint on the relation is a <a href="/facts/Logical_consequence/AyDXp4dn">logical consequence</a> of the definition of keys and domains, and enforcing key and domain restraints and conditions causes all constraints to be met. Thus, it avoids all non-<a href="/facts/Temporal_database/mrT0DKfy">temporal</a> anomalies.
The reason to use domain/key normal form is to avoid having general constraints in the database that are not clear domain or key constraints. Most databases can easily test domain and key constraints on attributes. General constraints however would normally require special database programming in the form of <a href="/facts/Stored_procedure/50xRehaI">stored procedures</a> (often of the <a href="/facts/Database_trigger/yhI7KW6H">trigger</a> variety) that are expensive to maintain and expensive for the database to execute. Therefore, general constraints are split into domain and key constraints.
It's much easier to build a new database in domain/key normal form than it is to convert from databases on lesser normal forms which may contain numerous anomalies. However, successfully building a domain/key normal form database remains a difficult task, even for experienced database programmers. Thus, while the domain/key normal form eliminates the problems found in most databases, it tends to be the most costly normal form to achieve. However, failing to achieve the domain/key normal form may carry long-term, hidden costs due to anomalies which appear in databases adhering only to lower normal forms over time.
The <a href="/facts/Third_normal_form/44D2DWId">third normal form</a>, <a href="/facts/Boyce%25E2%2580%2593Codd_normal_form/4EupLQ2n">Boyce–Codd normal form</a>, <a href="/facts/Fourth_normal_form/NRHGMe5u">fourth normal form</a> and <a href="/facts/Fifth_normal_form/HK3jwcuW">fifth normal form</a> are special cases of the domain/key normal form. All have either <a href="/facts/Functional_dependency/aLfwfUNk">functional</a>, <a href="/facts/Multivalued_dependency/a9b3na1u">multi-valued</a> or <a href="/facts/Lossless_join_decomposition/mhoDRA4j">join</a> dependencies that can be converted into <a href="/facts/Superkey/SbRlIoXN">superkeys</a>. The domains on those normal forms were unconstrained so all domain constraints are satisfied. However, transforming a higher normal form into domain/key normal form is not always a dependency-preserving transformation and therefore not always possible.

Domain-key normal form open-in-new

Domain-key normal form