Back to marketplace

Normalization (P2)

No description yet. This curated deck is ready for daily study.

Total cards: 8•Content version: v4•Public deck•Updated: 8/1/2026

Card preview (8)

#1
Front (Question)

Normalization

Back (Answer)

When larger tables in a database are divided into smaller tables to improve data integrity and reduce data redundancy.

#2
Front (Question)

3 outlined reasons to use normalization

Back (Answer)

• Reduced data redundancy (saves up memory space) • Reduced table complexity (Makes querying less error-prone) • Makes sure data is stored logically (Makes querying more efficient)

#3
Front (Question)

1NF - 5 characteristics

Back (Answer)

• Eliminate duplicate attributes • Eliminate attributes with multiple values (only atomic attributes) • Create separate tables for each group of related data • Ensure that there is a primary/composite key • Ensure that all records are unique

#4
Front (Question)

2NF - 2 characteristics

Back (Answer)

• Meets all requirements for 1NF • Eliminates partial dependency

#5
Front (Question)

3NF - 2 characteristics

Back (Answer)

• Meet all requirements for 2NF • Eliminates transitive dependency

#6
Front (Question)

Partial Dependency

Back (Answer)

When a non-prime attribute is dependent on only part of a composite key

#7
Front (Question)

Transitive Dependency

Back (Answer)

When a non-prime attribute is dependent on another non-prime attribute which is dependent on the primary key

#8
Front (Question)

How to fix partial dependency, transitive dependency and what is similar in both solutions?

Back (Answer)

Partial dependency? 🔄 Split off attributes that depend on part of a composite key. Transitive dependency? 🔁 Split off attributes that depend on another non-key attribute. In both cases? ✅ Use foreign keys to keep the relationships intact.