Why grouping is needed in SQL - See It in Action

Understanding Why Grouping is Needed in SQL

📖 Scenario: You work at a small bookstore. You have a list of sales records showing which book was sold and how many copies. You want to find out how many copies of each book were sold in total.

🎯 Goal: Build a SQL query that groups sales by book title and calculates the total copies sold for each book.

📋 What You'll Learn

Create a table called sales with columns book_title and copies_sold

Insert the exact sales data provided

Write a SQL query that groups the sales by book_title

Use SUM() to calculate total copies sold per book

💡 Why This Matters

🌍 Real World

Grouping data is common in sales reports, inventory summaries, and any situation where you want totals or averages per category.

💼 Career

Understanding GROUP BY is essential for data analysis, reporting, and writing effective SQL queries in many jobs.

1

Create the sales table and insert data

Create a table called sales with columns book_title (text) and copies_sold (integer). Insert these exact rows: ('The Hobbit', 3), ('1984', 5), ('The Hobbit', 2), ('Dune', 4), ('1984', 1).

SQL

-- Create table sales and insert data
-- Your code here

Hint

Use CREATE TABLE to make the table and INSERT INTO to add the rows.

2

Add a query to group sales by book

Write a SQL query that selects book_title and the total copies sold for each book. Use GROUP BY book_title to group the rows by book title.

SQL

CREATE TABLE sales (book_title TEXT, copies_sold INTEGER);
INSERT INTO sales (book_title, copies_sold) VALUES
('The Hobbit', 3),
('1984', 5),
('The Hobbit', 2),
('Dune', 4),
('1984', 1);

-- Write a query to group sales by book_title
-- Your code here

Hint

Use SUM(copies_sold) to add copies sold per book and GROUP BY book_title to group rows.

3

Explain why grouping is needed

Add a comment explaining why GROUP BY is needed in this query to get total copies sold per book.

SQL

CREATE TABLE sales (book_title TEXT, copies_sold INTEGER);
INSERT INTO sales (book_title, copies_sold) VALUES
('The Hobbit', 3),
('1984', 5),
('The Hobbit', 2),
('Dune', 4),
('1984', 1);

SELECT book_title, SUM(copies_sold) AS total_copies
FROM sales
GROUP BY book_title;

-- Add a comment explaining why GROUP BY is needed
-- Your code here

Hint

Think about how grouping helps add up sales for each book instead of all sales together.

4

Complete the query with ordering

Add ORDER BY total_copies DESC to the query to show books with the highest total copies sold first.

SQL

CREATE TABLE sales (book_title TEXT, copies_sold INTEGER);
INSERT INTO sales (book_title, copies_sold) VALUES
('The Hobbit', 3),
('1984', 5),
('The Hobbit', 2),
('Dune', 4),
('1984', 1);

SELECT book_title, SUM(copies_sold) AS total_copies
FROM sales
GROUP BY book_title
-- Add ORDER BY to sort by total_copies descending
-- Your code here

Hint

Use ORDER BY total_copies DESC to sort results from highest to lowest total copies sold.

Practice

1. Why do we use GROUP BY in SQL queries?

easy

A. To organize rows into groups based on column values

B. To sort the results alphabetically

C. To delete duplicate rows from the table

D. To change the data type of a column

Solution

1. Step 1: Understand the purpose of grouping

   Grouping organizes rows that share the same value in specified columns into sets.

2. Step 2: Identify what GROUP BY does in SQL

   It collects rows into groups so aggregate functions like SUM or COUNT can be applied per group.

3. Final Answer:

   To organize rows into groups based on column values -> Option A

4. Quick Check:

   Grouping = Organizing rows by column values [OK]

Hint: Grouping collects rows by column values for summary [OK]

Common Mistakes:

• Confusing grouping with sorting
• Thinking grouping deletes duplicates
• Assuming grouping changes data types

2. Which of the following is the correct syntax to group data by the column department?

easy

A. SELECT department, COUNT(*) FROM employees GROUP BY department;

B. SELECT department, COUNT(*) FROM employees ORDER BY department;

C. SELECT department, COUNT(*) FROM employees WHERE department;

D. SELECT department, COUNT(*) FROM employees HAVING department;

Solution

1. Step 1: Identify the correct clause for grouping

   The GROUP BY clause groups rows by column values.

2. Step 2: Check each option's syntax

   SELECT department, COUNT(*) FROM employees GROUP BY department; uses GROUP BY department, which is correct. Others use clauses for sorting, filtering, or incomplete syntax.

3. Final Answer:

   SELECT department, COUNT(*) FROM employees GROUP BY department; -> Option A

4. Quick Check:

   Correct grouping uses GROUP BY [OK]

Hint: Use GROUP BY to group, not ORDER BY or WHERE [OK]

Common Mistakes:

• Using ORDER BY instead of GROUP BY
• Using WHERE to filter groups
• Using HAVING without aggregation

3. Given the table sales with columns region and amount, what will this query return?

SELECT region, SUM(amount) FROM sales GROUP BY region;

medium

A. Syntax error due to missing WHERE clause

B. List of all sales amounts without grouping

C. Sum of all sales amounts without region breakdown

D. Total sales amount for each region

Solution

1. Step 1: Understand the query components

   The query groups rows by region and sums amount per group.

2. Step 2: Predict the output

   It returns one row per region with the total sales amount for that region.

3. Final Answer:

   Total sales amount for each region -> Option D

4. Quick Check:

   GROUP BY region + SUM(amount) = total per region [OK]

Hint: GROUP BY + SUM = totals per group [OK]

Common Mistakes:

• Thinking it sums all rows ignoring groups
• Expecting a syntax error without WHERE
• Confusing grouping with filtering

4. Identify the error in this query:

SELECT department, COUNT(employee_id) FROM employees;

medium

A. SELECT must include WHERE clause

B. Missing GROUP BY clause for department

C. COUNT cannot be used with employee_id

D. employee_id should be in HAVING clause

Solution

1. Step 1: Analyze the SELECT and aggregation

   The query selects department and counts employee_id but lacks grouping.

2. Step 2: Understand SQL rules for aggregation

   When using aggregate functions with other columns, those columns must be in GROUP BY.

3. Final Answer:

   Missing GROUP BY clause for department -> Option B

4. Quick Check:

   Aggregate + column needs GROUP BY [OK]

Hint: Use GROUP BY with non-aggregated columns [OK]

Common Mistakes:

• Omitting GROUP BY with aggregates
• Misusing HAVING for columns
• Thinking COUNT can't use column names

5. You want to find the average salary per job title but only for job titles with more than 5 employees. Which query correctly uses grouping and filtering?

hard

A. SELECT job_title, AVG(salary) FROM employees GROUP BY job_title WHERE COUNT(*) > 5;

B. SELECT job_title, AVG(salary) FROM employees WHERE COUNT(*) > 5 GROUP BY job_title;

C. SELECT job_title, AVG(salary) FROM employees GROUP BY job_title HAVING COUNT(*) > 5;

D. SELECT job_title, AVG(salary) FROM employees HAVING COUNT(*) > 5 GROUP BY job_title;

Solution

1. Step 1: Understand filtering groups with HAVING

   To filter groups after aggregation, use HAVING, not WHERE.

2. Step 2: Check query order and clauses

   SELECT job_title, AVG(salary) FROM employees GROUP BY job_title HAVING COUNT(*) > 5; correctly groups by job_title and filters groups with more than 5 employees using HAVING.

3. Final Answer:

   SELECT job_title, AVG(salary) FROM employees GROUP BY job_title HAVING COUNT(*) > 5; -> Option C

4. Quick Check:

   Filter groups with HAVING after GROUP BY [OK]

Hint: Use HAVING to filter groups, not WHERE [OK]

Common Mistakes:

• Using WHERE to filter aggregated groups
• Placing HAVING before GROUP BY
• Confusing clause order in SQL