Second Normal Form (2NF) in DBMS Theory - Step-by-Step Execution

Concept Flow - Second Normal Form (2NF)

Start with 1NF table

↓

Check for composite primary key?

No→Already in 2NF

Yes↓

Check for partial dependencies

↓

Yes

↓

Remove partial [Table is in 2NF

↓

Create new tables

↓

Result: Tables in 2NF

Start with a table in 1NF, check if it has a composite key. If yes, find and remove partial dependencies by splitting tables, resulting in 2NF.

Execution Sample

DBMS Theory

Table: Orders
PK: (OrderID, ProductID)
Attributes: OrderDate, ProductName, Quantity

Check partial dependencies

This table has a composite key and attributes; we check if any attribute depends only on part of the key.

Analysis Table

Step	Action	Check	Result	Next Step
1	Start with Orders table	Is table in 1NF?	Yes	Check composite key
2	Check primary key	Is key composite?	Yes (OrderID, ProductID)	Check partial dependencies
3	Check OrderDate dependency	Depends on full key?	Depends only on OrderID (partial)	Partial dependency found
4	Check ProductName dependency	Depends on full key?	Depends only on ProductID (partial)	Partial dependency found
5	Remove partial dependencies	Split table into Orders and Products	Orders(OrderID, OrderDate), Products(ProductID, ProductName)	Tables now in 2NF
6	Final check	Are there partial dependencies?	No	Stop

💡 No partial dependencies remain; tables are in Second Normal Form.

State Tracker

Variable	Start	After Step 3	After Step 4	After Step 5	Final
Table	Orders(OrderID, ProductID, OrderDate, ProductName, Quantity)	Partial dependency on OrderID found	Partial dependency on ProductID found	Split into Orders and Products tables	Orders and Products tables in 2NF

Key Insights - 3 Insights

Why do we check if the primary key is composite?

Because Second Normal Form only applies when the primary key has more than one column, as partial dependencies can only exist then (see execution_table step 2).

What is a partial dependency?

A partial dependency is when a non-key attribute depends on only part of a composite primary key, not the whole key (see execution_table steps 3 and 4).

Why do we split the table to remove partial dependencies?

Splitting removes attributes that depend on part of the key into separate tables, ensuring all attributes depend on the full key, achieving 2NF (see execution_table step 5).

Visual Quiz - 3 Questions

Look at the execution table, at which step do we find the first partial dependency?

A Step 3

B Step 4

C Step 2

D Step 5

💡 Hint

Check the 'Result' column for 'Partial dependency found' in the execution_table.

According to the variable tracker, what is the state of the table after step 5?

A Still one table with partial dependencies

B Table removed all attributes

C Split into Orders and Products tables

D Table has no primary key

💡 Hint

Look at the 'After Step 5' column in variable_tracker.

If the primary key was not composite, what would the execution table say at step 2?

A Is key composite? Yes

B Is key composite? No

C Partial dependencies found

D Split tables

💡 Hint

Refer to execution_table step 2 about checking if the key is composite.

Concept Snapshot

Second Normal Form (2NF):
- Applies to tables with composite primary keys.
- Removes partial dependencies (attributes depending on part of the key).
- Achieved by splitting tables to ensure all attributes depend on the full key.
- Ensures better data organization and reduces redundancy.

Full Transcript

Second Normal Form (2NF) is a database design rule that builds on First Normal Form (1NF). It applies only when a table has a composite primary key, meaning the key is made of more than one column. The main goal is to remove partial dependencies, which happen when some columns depend on only part of the key, not the whole key. To fix this, we split the table into smaller tables so that each non-key attribute depends on the entire primary key. This process reduces data duplication and improves organization. The execution steps start by checking if the table is in 1NF, then if the key is composite. If yes, we look for partial dependencies and remove them by creating new tables. When no partial dependencies remain, the tables are in 2NF.

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