liveBook · Manning

Functional dependency

A functional dependency is a relational constraint in which one set of attributes uniquely determines the values of another set of attributes.

How 2 Manning books explain it

100 SQL Server Mistakes and How to Avoid Them

A functional dependency is a relationship in which one set of attributes determines the value of another set of attributes.

How it is used
Uses functional dependency to test relations while moving a schema from 1NF to 2NF and 3NF.
How deep it goes
Explains partial and transitive dependencies through schema changes, without formal dependency notation or algorithms.
Examples
Uses Product Type Name and Product Type Description to expose a partial dependency.
What you can do after
Apply 2NF and 3NF checks by separating attributes determined by only part of a key or by nonprime attributes.

Read how 100 SQL Server Mistakes and How to Avoid Them explains functional dependency →

Grokking Relational Database Design

A functional dependency is a constraint in which a value or set of values in one or more columns uniquely determines the value of another column.

How it is used
Uses column-determination rules to normalize tables and check BCNF and 3NF designs.
How deep it goes
Explains direction, single-column and composite dependencies, and transitive chains, then stops short of edge cases.
Examples
Uses employee, purchase, product, supplier, department, and purchase_product tables to demonstrate dependencies and decomposition.
What you can do after
Apply it via normalization by locating wrongly dependent columns and moving them into appropriately keyed tables.

Read how Grokking Relational Database Design explains functional dependency →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.