Why JOIN with aggregate functions in MySQL? - Purpose & Use Cases

The Big Idea

What if you could instantly see totals from different lists without counting by hand?

The Scenario

Imagine you have two lists: one with customers and another with their orders. You want to find out how many orders each customer made. Doing this by hand means flipping back and forth between lists, counting orders for each customer manually.

The Problem

Manually counting orders is slow and easy to mess up. You might forget some orders or count some twice. It's hard to keep track when the lists grow big, and updating counts every time new orders come in is a headache.

The Solution

Using JOIN with aggregate functions in SQL lets you combine customer and order data automatically. You can count orders per customer in one simple query, saving time and avoiding mistakes.

Before vs After

✗ Before

For each customer:
  count = 0
  For each order:
    if order.customer_id == customer.id:
      count += 1
  print(customer.name, count)

✓ After

SELECT customers.name, COUNT(orders.id) AS order_count
FROM customers
LEFT JOIN orders ON customers.id = orders.customer_id
GROUP BY customers.name;

What It Enables

This lets you quickly summarize and analyze related data from multiple tables, unlocking powerful insights with minimal effort.

Real Life Example

A store manager can instantly see which customers buy the most products, helping to plan promotions and rewards.

Key Takeaways

Manual counting across lists is slow and error-prone.

JOIN with aggregate functions automates combining and summarizing data.

This makes data analysis faster, easier, and more reliable.

Practice

1. What does the following SQL query do?
SELECT department, COUNT(employee_id) FROM employees JOIN departments ON employees.dept_id = departments.id GROUP BY department;

easy

A. Counts employees in each department by joining employees and departments tables.

B. Lists all employees without grouping by department.

C. Calculates the average salary per department.

D. Deletes employees who are not assigned to any department.

Solution

1. Step 1: Understand the JOIN operation

   The query joins the employees and departments tables using the department ID to combine related data.

2. Step 2: Analyze the GROUP BY and COUNT

   It groups the results by department and counts the number of employees in each group.

3. Final Answer:

   Counts employees in each department by joining employees and departments tables. -> Option A

4. Quick Check:

   JOIN + GROUP BY + COUNT = Employee count per department [OK]

Hint: JOIN tables, GROUP BY key, then apply COUNT [OK]

Common Mistakes:

• Ignoring GROUP BY causes wrong aggregation
• Using COUNT without JOIN returns incomplete data
• Confusing COUNT with SUM or AVG

2. Which of the following is the correct syntax to get the total sales per customer using JOIN and SUM?
SELECT customers.name, SUM(orders.amount) FROM customers JOIN orders ON customers.id = orders.customer_id GROUP BY customers.name;

easy

A. SELECT customers.name, SUM(orders.amount) FROM customers LEFT JOIN orders GROUP BY customers.name;

B. SELECT customers.name, SUM(orders.amount) FROM customers JOIN orders WHERE customers.id = orders.customer_id GROUP BY customers.name;

C. SELECT customers.name, SUM(orders.amount) FROM customers JOIN orders ON customers.id = orders.customer_id GROUP BY customers.name;

D. SELECT customers.name, SUM(orders.amount) FROM customers, orders GROUP BY customers.name;

Solution

1. Step 1: Check JOIN syntax

   SELECT customers.name, SUM(orders.amount) FROM customers JOIN orders ON customers.id = orders.customer_id GROUP BY customers.name; uses correct INNER JOIN syntax with ON clause to link customers and orders.

2. Step 2: Verify GROUP BY and SUM usage

   SELECT customers.name, SUM(orders.amount) FROM customers JOIN orders ON customers.id = orders.customer_id GROUP BY customers.name; correctly groups by customer name and sums order amounts.

3. Final Answer:

   SELECT customers.name, SUM(orders.amount) FROM customers JOIN orders ON customers.id = orders.customer_id GROUP BY customers.name; -> Option C

4. Quick Check:

   JOIN with ON + GROUP BY + SUM = Correct syntax [OK]

Hint: Use JOIN ... ON ... with GROUP BY for aggregates [OK]

Common Mistakes:

• Using WHERE instead of ON in JOIN
• Missing ON clause causes syntax error
• Grouping by wrong column

3. Given tables:
employees(id, name, dept_id)
departments(id, department)
What is the output of this query?

SELECT d.department, COUNT(e.id) AS emp_count FROM employees e LEFT JOIN departments d ON e.dept_id = d.id GROUP BY d.department ORDER BY emp_count DESC;

medium

A. Syntax error due to missing GROUP BY column.

B. List of departments with employee counts, including departments with zero employees.

C. List of employees with their department names.

D. List of departments with employee counts, excluding departments with zero employees.

Solution

1. Step 1: Understand LEFT JOIN effect

   FROM employees e LEFT JOIN departments d ON e.dept_id = d.id includes all employees and matching departments if they exist. Departments with no employees do not appear because no employee row matches them.

2. Step 2: GROUP BY and COUNT behavior

   Grouping by d.department counts employees only for departments that have at least one employee (count >=1). Departments with zero employees are excluded.

3. Final Answer:

   List of departments with employee counts, excluding departments with zero employees. -> Option D

4. Quick Check:

   LEFT JOIN from employees + GROUP BY department excludes zero counts [OK]

Hint: LEFT JOIN keeps all left rows, COUNT counts matches [OK]

Common Mistakes:

• Assuming INNER JOIN behavior excludes zero counts
• Confusing COUNT(*) with COUNT(column)
• Ignoring NULL values in grouping

4. Identify the error in this query:

SELECT d.department, COUNT(e.id) FROM employees e JOIN departments d ON e.dept_id = d.id WHERE e.salary > 50000 GROUP BY e.dept_id;

medium

A. GROUP BY should use d.department instead of e.dept_id.

B. Missing HAVING clause for salary filter.

C. COUNT(e.id) cannot be used with JOIN.

D. ON clause is incorrect syntax.

Solution

1. Step 1: Check GROUP BY columns

   The SELECT lists d.department but GROUP BY uses e.dept_id, causing mismatch.

2. Step 2: Fix GROUP BY to match SELECT

   GROUP BY should use d.department or include it to avoid errors.

3. Final Answer:

   GROUP BY should use d.department instead of e.dept_id. -> Option A

4. Quick Check:

   GROUP BY columns must match SELECT non-aggregates [OK]

Hint: GROUP BY columns must match SELECT non-aggregates [OK]

Common Mistakes:

• Grouping by wrong or missing columns
• Using WHERE instead of HAVING for aggregates
• Incorrect JOIN ON syntax

5. You have tables:
orders(order_id, customer_id, amount)
customers(customer_id, name)
Write a query to find customers who have total orders amount greater than 1000, including customers with no orders showing zero total.
Which query is correct?

hard

A. SELECT c.name, SUM(o.amount) AS total FROM customers c LEFT JOIN orders o ON c.customer_id = o.customer_id WHERE total > 1000 GROUP BY c.name;

B. SELECT c.name, COALESCE(SUM(o.amount), 0) AS total FROM customers c LEFT JOIN orders o ON c.customer_id = o.customer_id GROUP BY c.name HAVING total > 1000;

C. SELECT c.name, SUM(o.amount) AS total FROM customers c JOIN orders o ON c.customer_id = o.customer_id GROUP BY c.name HAVING total > 1000;

D. SELECT c.name, SUM(o.amount) AS total FROM customers c LEFT JOIN orders o ON c.customer_id = o.customer_id GROUP BY c.name WHERE total > 1000;

Solution

1. Step 1: Use LEFT JOIN to include customers without orders

   LEFT JOIN ensures all customers appear, even if no matching orders exist.

2. Step 2: Use COALESCE to convert NULL sums to zero and HAVING to filter totals

   COALESCE replaces NULL with 0; HAVING filters groups by aggregate result.

3. Final Answer:

   SELECT c.name, COALESCE(SUM(o.amount), 0) AS total FROM customers c LEFT JOIN orders o ON c.customer_id = o.customer_id GROUP BY c.name HAVING total > 1000; -> Option B

4. Quick Check:

   LEFT JOIN + COALESCE + HAVING filters totals correctly [OK]

Hint: Use LEFT JOIN + COALESCE + HAVING for conditional aggregates [OK]

Common Mistakes:

• Using WHERE instead of HAVING for aggregate filters
• Ignoring NULL sums for customers without orders
• Using INNER JOIN excludes customers with zero orders