Second Normal Form (2NF) in DBMS Theory - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main goal of Second Normal Form (2NF)?

The main goal of 2NF is to remove partial dependencies, meaning every non-key attribute must depend on the whole primary key, not just part of it.

beginner

What kind of dependency does 2NF eliminate?

2NF eliminates partial dependency, where a non-key attribute depends only on a part of a composite primary key.

beginner

True or False: A table with a single-column primary key is always in 2NF.

True. Since there is no composite key, partial dependency cannot exist, so the table is automatically in 2NF if it is in 1NF.

intermediate

Why is 2NF important in database design?

2NF helps reduce data redundancy and update anomalies by ensuring that attributes depend on the entire primary key, making data more consistent.

beginner

What must a table satisfy before it can be in Second Normal Form?

It must first be in First Normal Form (1NF), meaning it has no repeating groups and each field contains atomic values.

Which of the following best describes a table in 2NF?

A No transitive dependency

B No repeating groups or arrays

C No partial dependency on any part of the primary key

D No foreign keys

2NF requires that every non-key attribute depends on the whole primary key, eliminating partial dependencies.

If a table has a single-column primary key, it is:

A Always in 2NF

B Never in 2NF

C Only in 1NF

D Only in 3NF

With a single-column primary key, partial dependency cannot exist, so the table is always in 2NF if it is in 1NF.

What problem does 2NF mainly address?

A Partial dependency

B Transitive dependency

C Duplicate rows

D Missing primary key

2NF removes partial dependencies where attributes depend on part of a composite key.

Before applying 2NF, a table must be in which normal form?

A 4NF

B 3NF

C BCNF

D 1NF

2NF builds on 1NF, so the table must first be in First Normal Form.

Which of these is a sign that a table is NOT in 2NF?

A All attributes depend on the whole key

B A non-key attribute depends only on part of a composite key

C No repeating groups

D No null values

Partial dependency means a non-key attribute depends on only part of the composite key, violating 2NF.

Explain what Second Normal Form (2NF) means and why it is important in database design.

Think about how attributes relate to the whole primary key.

Describe the steps to check if a table is in Second Normal Form (2NF).

Start from 1NF and focus on dependencies.

Practice

1. Which of the following best describes the Second Normal Form (2NF) in database normalization?

easy

A. It requires the table to have no duplicate rows.

B. It removes transitive dependencies.

C. It removes partial dependencies on a composite primary key.

D. It ensures all columns are atomic.

Solution

1. Step 1: Understand 2NF definition

   2NF requires that every non-key attribute is fully functionally dependent on the entire primary key, not just part of it.

2. Step 2: Compare options

   It removes partial dependencies on a composite primary key correctly states removal of partial dependencies on composite keys. Other options describe 1NF (atomic columns), uniqueness, or 3NF (transitive dependencies).

3. Final Answer:

   It removes partial dependencies on a composite primary key. -> Option C

4. Quick Check:

   2NF = Remove partial dependencies [OK]

Hint: 2NF removes partial dependencies on composite keys [OK]

Common Mistakes:

• Confusing 2NF with 1NF or 3NF
• Thinking 2NF removes transitive dependencies
• Believing 2NF applies to single-column keys only

2. Which of the following is the correct condition for a table to be in Second Normal Form (2NF)?

easy

A. Every non-key attribute must depend on the whole primary key.

B. All attributes must be unique.

C. There must be no transitive dependencies.

D. The table must have no repeating groups.

Solution

1. Step 1: Recall 2NF condition

   2NF requires that non-key attributes depend on the entire primary key, not just part of it.

2. Step 2: Analyze options

   Every non-key attribute must depend on the whole primary key matches this condition. The table must have no repeating groups describes 1NF, There must be no transitive dependencies describes 3NF, and All attributes must be unique is unrelated to normalization.

3. Final Answer:

   Every non-key attribute must depend on the whole primary key. -> Option A

4. Quick Check:

   2NF = Full dependency on primary key [OK]

Hint: Non-key attributes depend on entire key in 2NF [OK]

Common Mistakes:

• Mixing 2NF with 1NF or 3NF conditions
• Assuming uniqueness means 2NF
• Ignoring composite keys in dependency

3. Consider a table with columns StudentID, CourseID, and InstructorName. The primary key is a composite of StudentID and CourseID. If InstructorName depends only on CourseID, what is the normalization status of this table?

medium

A. The table is not in 2NF due to partial dependency.

B. The table is in 2NF.

C. The table is in 3NF.

D. The table violates 1NF.

Solution

1. Step 1: Identify dependencies

   InstructorName depends only on CourseID, which is part of the composite key (StudentID, CourseID).

2. Step 2: Check for partial dependency

   Since InstructorName depends on only part of the key, this is a partial dependency, violating 2NF.

3. Final Answer:

   The table is not in 2NF due to partial dependency. -> Option A

4. Quick Check:

   Partial dependency means not 2NF [OK]

Hint: Partial dependency on part of key breaks 2NF [OK]

Common Mistakes:

• Assuming table is 2NF because it has a composite key
• Confusing 2NF with 3NF
• Ignoring partial dependencies

4. A table has columns OrderID, ProductID, ProductName, and Quantity. The primary key is composite: (OrderID, ProductID). The ProductName depends only on ProductID. What is the error in this design regarding 2NF?

medium

A. There is a transitive dependency violating 2NF.

B. The primary key is not composite.

C. The table is already in 2NF.

D. There is a partial dependency violating 2NF.

Solution

1. Step 1: Identify dependency of ProductName

   ProductName depends only on ProductID, part of the composite key (OrderID, ProductID).

2. Step 2: Recognize partial dependency

   This partial dependency violates 2NF, which requires full dependency on the entire key.

3. Final Answer:

   There is a partial dependency violating 2NF. -> Option D

4. Quick Check:

   Partial dependency breaks 2NF [OK]

Hint: Partial dependency on part of composite key breaks 2NF [OK]

Common Mistakes:

• Confusing partial with transitive dependency
• Thinking primary key must be single column for 2NF
• Assuming table is normalized without checking dependencies

5. You have a table with columns EmployeeID, ProjectID, EmployeeName, and ProjectName. The primary key is composite: (EmployeeID, ProjectID). Both EmployeeName and ProjectName depend only on their respective single keys (EmployeeID and ProjectID). How should you redesign the tables to achieve 2NF?

hard

A. Keep one table but remove EmployeeName and ProjectName columns.

B. Split into three tables: Employee(EmployeeID, EmployeeName), Project(ProjectID, ProjectName), and Assignment(EmployeeID, ProjectID).

C. Add a new composite key including EmployeeName and ProjectName.

D. No changes needed; the table is already in 2NF.

Solution

1. Step 1: Identify partial dependencies

   EmployeeName depends only on EmployeeID, and ProjectName depends only on ProjectID, parts of the composite key.

2. Step 2: Normalize by splitting tables

   To remove partial dependencies, create separate tables for Employee and Project details, and a linking table for assignments.

3. Final Answer:

   Split into three tables: Employee(EmployeeID, EmployeeName), Project(ProjectID, ProjectName), and Assignment(EmployeeID, ProjectID). -> Option B

4. Quick Check:

   Separate tables remove partial dependencies [OK]

Hint: Split tables to remove partial dependencies for 2NF [OK]

Common Mistakes:

• Trying to keep all data in one table
• Adding composite keys incorrectly
• Ignoring partial dependencies on composite keys