Denormalization and when to use it in SQL - Step-by-Step Execution

Concept Flow - Denormalization and when to use it

Start with Normalized Tables

↓

Identify Performance Bottlenecks

↓

Decide to Denormalize

↓

Add Redundant Data to Tables

↓

Simplify Queries & Improve Speed

↓

Manage Data Consistency Carefully

↓

End

Denormalization adds extra data to tables to speed up queries but requires careful updates to keep data consistent.

Execution Sample

SQL

SELECT orders.id, customers.name, orders.total
FROM orders
JOIN customers ON orders.customer_id = customers.id;

This query joins two normalized tables to get order info with customer names.

Execution Table

Step	Action	Tables Accessed	Data Retrieved	Resulting Output
1	Scan orders table	orders	order ids, customer_ids, totals	Partial order data loaded
2	Scan customers table	customers	customer ids, names	Partial customer data loaded
3	Join orders.customer_id = customers.id	orders, customers	matched rows	Combined order and customer info
4	Select columns id, name, total	joined data	order id, customer name, order total	Final result set with 3 columns
5	Return result	N/A	N/A	Query complete with joined data

💡 Query ends after joining normalized tables; can be slow if tables are large.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
orders_data	empty	loaded order rows	loaded order rows	joined with customers	joined with customers	final joined data
customers_data	empty	empty	loaded customer rows	joined with orders	joined with orders	final joined data
result_set	empty	empty	empty	empty	selected columns	final output rows

Key Moments - 3 Insights

Why does joining normalized tables sometimes slow down queries?

Because the database must look up matching rows in multiple tables (see execution_table steps 1-3), which takes time especially with large data.

How does denormalization improve query speed?

By storing redundant data in one table, queries avoid joins (like in execution_table step 3), so data is fetched faster.

What is the risk of denormalization?

Data inconsistency can happen if redundant data is not updated everywhere it appears, requiring careful management.

Visual Quiz - 3 Questions

Look at the execution_table, at which step does the join between tables happen?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Check the 'Action' column in execution_table for the step mentioning 'Join'.

According to variable_tracker, what is the state of 'result_set' after Step 4?

A selected columns

B joined with customers

C empty

D loaded order rows

💡 Hint

Look at the 'result_set' row under 'After Step 4' in variable_tracker.

If we denormalize by adding customer names directly to orders, which execution_table step can be skipped?

A Step 2

B Step 3

C Step 1

D Step 4

💡 Hint

Denormalization avoids the need to join tables, so the join step is skipped.

Concept Snapshot

Denormalization means adding extra data to tables to avoid joins.
It speeds up queries by reducing table lookups.
Use it when read speed matters more than storage or update complexity.
Be careful to update redundant data to keep consistency.
Typical in reporting or caching scenarios.

Full Transcript

Denormalization is a database technique where we add redundant data to tables to make queries faster. Normally, data is split into multiple tables (normalized) to avoid duplication. But joining these tables can slow queries down. Denormalization stores some repeated data in one table, so queries don't need to join as much. This improves speed but means we must update data carefully to avoid inconsistencies. For example, instead of joining orders and customers tables to get customer names, we store the customer name directly in the orders table. This way, queries run faster but updates to customer names must be done in multiple places. Denormalization is useful when query speed is more important than storage or update simplicity.

Practice

1. What is the main purpose of denormalization in a database?

easy

A. To split data into many small tables

B. To remove all duplicate data for storage efficiency

C. To enforce strict data integrity rules

D. To add redundant data to speed up read operations

Solution

1. Step 1: Understand denormalization goal and compare options

   Denormalization means adding repeated data to reduce complex joins and speed up reading. Only "To add redundant data to speed up read operations" describes adding redundant data to improve read speed, which matches denormalization.

2. Final Answer:

   To add redundant data to speed up read operations -> Option D

3. Quick Check:

   Denormalization = add redundant data for faster reads [OK]

Hint: Denormalization means adding data to read faster, not removing it [OK]

Common Mistakes:

• Confusing denormalization with normalization
• Thinking denormalization removes duplicates
• Believing denormalization enforces stricter rules

2. Which of the following best represents a denormalized table structure?

easy

A. Separate tables for customers and orders linked by customer_id

B. A table with repeated customer address fields in each order record

C. A table with only unique keys and no repeated data

D. A table with foreign keys but no repeated columns

Solution

1. Step 1: Identify denormalized structure and match to options

   Denormalized tables store repeated data, like customer address repeated in each order. "A table with repeated customer address fields in each order record" shows repeated fields in one table, which is denormalization. Others show normalized forms.

2. Final Answer:

   A table with repeated customer address fields in each order record -> Option B

3. Quick Check:

   Repeated fields in one table = denormalized [OK]

Hint: Look for repeated fields in one table to spot denormalization [OK]

Common Mistakes:

• Choosing normalized table structures
• Confusing foreign keys with denormalization
• Ignoring repeated data presence

3. Given a denormalized table Orders with columns OrderID, CustomerName, and CustomerAddress repeated in every row, what is a likely effect when updating a customer's address?

medium

A. You must update the address in every order row for that customer

B. Updating one row automatically updates all related rows

C. No update is needed because address is stored separately

D. The database prevents duplicate addresses

Solution

1. Step 1: Understand denormalized update effects and analyze options

   In denormalized tables, repeated data means updates must be applied to all copies to keep consistency. Only "You must update the address in every order row for that customer" correctly states that all rows must be updated manually.

2. Final Answer:

   You must update the address in every order row for that customer -> Option A

3. Quick Check:

   Repeated data requires multiple updates [OK]

Hint: Repeated data means multiple updates needed for consistency [OK]

Common Mistakes:

• Assuming one update changes all rows automatically
• Thinking address is stored separately in denormalized tables
• Believing database prevents duplicates in denormalized data

4. You have a denormalized table where customer phone numbers are repeated in many rows. You run this update:

UPDATE Orders SET CustomerPhone = '123-4567' WHERE CustomerID = 5;

but some rows still show old phone numbers. What is the most likely problem?

medium

A. The WHERE clause did not match all rows for CustomerID 5

B. Denormalization prevents updates to repeated data

C. CustomerPhone is a computed column and cannot be updated

D. The database automatically updates all rows, so this is impossible

Solution

1. Step 1: Analyze update query symptom and identify cause

   The update targets rows with CustomerID = 5, but some rows still have old data, meaning some rows were missed. Most likely, some rows have incorrect or missing CustomerID values, so the WHERE clause did not match them.

2. Final Answer:

   The WHERE clause did not match all rows for CustomerID 5 -> Option A

3. Quick Check:

   Update misses rows if WHERE condition is incomplete [OK]

Hint: Check WHERE clause matches all repeated rows in denormalized tables [OK]

Common Mistakes:

• Thinking denormalization blocks updates
• Assuming computed columns without checking
• Believing database auto-updates all duplicates

5. You want to speed up reporting queries that join Orders and Customers tables frequently. Which denormalization approach is best to improve read speed while managing data consistency?

hard

A. Remove customer details from Orders and query Customers each time

B. Keep separate tables and add more indexes on join keys

C. Add customer name and address columns directly into the Orders table

D. Duplicate Orders table for each customer

Solution

1. Step 1: Identify denormalization for faster reads and evaluate options

   Adding customer info directly into Orders reduces joins, speeding up queries. "Add customer name and address columns directly into the Orders table" adds repeated data for speed and requires careful updates, fitting denormalization best.

2. Final Answer:

   Add customer name and address columns directly into the Orders table -> Option C

3. Quick Check:

   Denormalize by adding repeated data to reduce joins [OK]

Hint: Denormalize by adding repeated fields to reduce joins for faster reads [OK]

Common Mistakes:

• Thinking indexing replaces denormalization
• Removing data increases joins and slows queries
• Duplicating entire tables causes complexity