Third normal form

Third normal form (3NF) is a <a href="/facts/Database_schema/DBq8fooY">database schema</a> design approach for <a href="/facts/Relational_database/pEKGmJLy">relational databases</a> which uses <a href="/facts/Database_normalization/uLCKbIBz">normalizing</a> principles to reduce the duplication of data, avoid <a href="/facts/Data_anomaly/uLCKbIBz">data anomalies</a>, ensure <a href="/facts/Referential_integrity/UJzY2tw5">referential integrity</a>, and simplify <a href="/facts/Data_management/Cykeqxc7">data management</a>. It was defined in 1971 by <a href="/facts/Edgar_F._Codd/QCSbPYkK">Edgar F. Codd</a>, an English computer scientist who invented the <a href="/facts/Relational_model/VFf4dDIU">relational model</a> for <a href="/facts/Database/VYcpkevb">database</a> management.
A <a href="/facts/Relation_(database)/Sj67AUyD">database relation</a> (e.g. a <a href="/facts/Table_(database)/5INvK1Vd">database table</a>) is said to meet third normal form standards if all the attributes (e.g. <a href="/facts/Column_(database)/WB91xSVs">database columns</a>) are <a href="/facts/Functional_dependency/aLfwfUNk">functionally dependent</a> on solely a <a href="/facts/Candidate_key/1SyxFj7C">key</a>, except the case of functional dependency whose right hand side is a prime attribute (an attribute which is strictly included into some key). Codd defined this as a relation in <a href="/facts/Second_normal_form/jBk8r5nL">second normal form</a> where all non-prime attributes depend only on the <a href="/facts/Candidate_key/1SyxFj7C">candidate keys</a> and do not have a <a href="/facts/Transitive_dependency/Lv8kTVJo">transitive dependency</a> on another key. 
A hypothetical example of a failure to meet third normal form would be a hospital database having a table of patients which included a column for the telephone number of their doctor. (The phone number is dependent on the doctor, rather than the patient, thus would be better stored in a table of doctors.) The negative outcome of such a design is that a doctor's number will be duplicated in the database if they have multiple patients, thus increasing both the chance of input error and the cost and risk of updating that number should it change (compared to a third normal form-compliant data model that only stores a doctor's number once on a doctor table).
Codd later realized that 3NF did not eliminate all undesirable data anomalies and developed a stronger version to address this in 1974, known as <a href="/facts/Boyce%25E2%2580%2593Codd_normal_form/4EupLQ2n">Boyce–Codd normal form</a>.

Third normal form open-in-new

Third normal form