Flashcards for:
Understanding Database Normalization Techniques

No using row order to convey information, no mixing data types within a single column, must have a primary key, and no repeating groups.

A primary key uniquely identifies each record in a table and ensures that rows are distinct and easily accessible.

A transitive dependency occurs when a non-key attribute depends on another non-key attribute. It’s removed in 3NF to ensure all non-key attributes depend only on the primary key.

Each progressive normal form imposes stricter rules to organize data, reduce redundancy, and ensure integrity, leading to more efficient and reliable databases.

To ensure that all information in a database cannot be decomposed into smaller join-dependent subsets without loss of information.

Insertion, update, and deletion anomalies.

In BCNF, every determinant must be a candidate key, meaning every attribute must depend solely on the whole key.

4NF eliminates multivalued dependencies that do not relate to the primary key by separating data into different tables.

To reduce redundancy and improve data integrity.

Because BCNF requires every determinant to be a candidate key, which often necessitates further decomposition of tables.

A transitive dependency occurs when a non-key attribute depends on another non-key attribute. It is resolved in 3NF by creating separate tables to eliminate indirect dependencies.

Separating tables for brand preferences, flavor preferences, and brand-flavor offerings to ensure all dependencies are explicitly represented.

To ensure that every non-key attribute is fully functionally dependent on the whole primary key, not just part of it.

Deletion, update, and insertion anomalies related to partial dependencies on a composite primary key.

A table storing combinations of models, colors, and styles, which aren’t dependent on each other, would require separation into different tables to achieve 4NF.