Why INNER JOIN with ON condition in SQL? - Purpose & Use Cases

The Big Idea

What if you could instantly connect pieces of data that seem separate, without any manual hassle?

The Scenario

Imagine you have two lists on paper: one with customer names and another with their orders. You want to find which customers made which orders. Doing this by hand means flipping back and forth between lists, matching names manually.

The Problem

Manually matching customers to orders is slow and mistakes happen easily. You might miss some matches or mix up orders. It's hard to keep track when lists grow big, and updating matches means rechecking everything again.

The Solution

INNER JOIN with ON condition lets the database automatically match rows from two tables based on a shared key, like customer ID. It quickly finds all matching pairs without errors, saving time and effort.

Before vs After

✗ Before

Look through customers list;
For each customer, search orders list for matching customer ID;
Write down matches.

✓ After

SELECT * FROM customers INNER JOIN orders ON customers.id = orders.customer_id;

What It Enables

This lets you combine related data from different tables instantly, making complex data easy to explore and analyze.

Real Life Example

A store wants to see which customers bought which products. Using INNER JOIN with ON condition, they get a list showing customer names alongside their orders, all in one place.

Key Takeaways

Manually matching data is slow and error-prone.

INNER JOIN with ON condition automates matching rows between tables.

This makes combining and analyzing related data fast and reliable.

Practice

1. What does an INNER JOIN do in SQL when used with an ON condition?

easy

A. It returns all rows from the first table regardless of matches.

B. It returns all rows from both tables, matching or not.

C. It returns all rows from the second table regardless of matches.

D. It returns only rows where the join condition matches in both tables.

Solution

1. Step 1: Understand INNER JOIN behavior

   INNER JOIN returns rows only when the join condition matches rows in both tables.

2. Step 2: Compare with other join types

   Unlike LEFT or RIGHT JOIN, INNER JOIN excludes rows without matches.

3. Final Answer:

   It returns only rows where the join condition matches in both tables. -> Option D

4. Quick Check:

   INNER JOIN = matching rows only [OK]

Hint: INNER JOIN keeps only matching rows from both tables [OK]

Common Mistakes:

• Thinking INNER JOIN returns unmatched rows
• Confusing INNER JOIN with LEFT JOIN
• Ignoring the ON condition effect

2. Which of the following is the correct syntax for an INNER JOIN with an ON condition between tables Employees and Departments on DepartmentID?

easy

A. SELECT * FROM Employees INNER JOIN Departments ON Employees.DepartmentID = Departments.DepartmentID;

B. SELECT * FROM Employees INNER JOIN Departments ON Employees.ID = Departments.ID;

C. SELECT * FROM Employees JOIN Departments USING DepartmentID;

D. SELECT * FROM Employees INNER JOIN Departments WHERE Employees.DepartmentID = Departments.DepartmentID;

Solution

1. Step 1: Identify correct INNER JOIN syntax

   The INNER JOIN requires the ON keyword followed by the join condition.

2. Step 2: Check the join condition correctness

   The join should be on Employees.DepartmentID = Departments.DepartmentID, not just ID or WHERE clause.

3. Final Answer:

   SELECT * FROM Employees INNER JOIN Departments ON Employees.DepartmentID = Departments.DepartmentID; -> Option A

4. Quick Check:

   INNER JOIN uses ON with condition [OK]

Hint: Use ON keyword with join condition for INNER JOIN [OK]

Common Mistakes:

• Using WHERE instead of ON for join condition
• Joining on wrong columns
• Omitting ON keyword

3. Given these tables:

Employees
ID | Name | DeptID
1 | Alice | 10
2 | Bob | 20
3 | Carol | 30

Departments
DeptID | DeptName
10 | Sales
20 | HR
40 | IT

What is the result of this query?

SELECT Employees.Name, Departments.DeptName FROM Employees INNER JOIN Departments ON Employees.DeptID = Departments.DeptID;

medium

A. [('Alice', 'Sales'), ('Bob', 'HR')]

B. [('Alice', 'Sales'), ('Bob', 'HR'), ('Carol', 'IT')]

C. [('Alice', 'Sales'), ('Carol', 'IT')]

D. [('Bob', 'HR'), ('Carol', 'IT')]

Solution

1. Step 1: Match Employees.DeptID with Departments.DeptID

   Employees have DeptIDs 10, 20, 30; Departments have 10, 20, 40.

2. Step 2: Find matching DeptIDs

   Matches are 10 and 20 only; 30 (Carol) has no matching department.

3. Final Answer:

   [('Alice', 'Sales'), ('Bob', 'HR')] -> Option A

4. Quick Check:

   INNER JOIN returns only matching DeptIDs [OK]

Hint: Only rows with matching DeptID appear in INNER JOIN result [OK]

Common Mistakes:

• Including unmatched rows like Carol's
• Confusing DeptID with ID
• Assuming all departments join

4. Consider this query:

SELECT e.Name, d.DeptName FROM Employees e INNER JOIN Departments d ON e.DeptID = d.ID;

Given Departments has column DeptID but no ID column, what is the issue?

medium

A. The query will join on wrong columns but still return rows.

B. The query will run but return no rows.

C. The query will cause a syntax error due to wrong column name.

D. The query will join correctly because aliases fix column names.

Solution

1. Step 1: Check column names in ON condition

   The query uses d.ID but Departments table has DeptID, not ID.

2. Step 2: Understand SQL error on invalid column

   Referencing a non-existent column causes a syntax or runtime error.

3. Final Answer:

   The query will cause a syntax error due to wrong column name. -> Option C

4. Quick Check:

   Wrong column in ON causes error [OK]

Hint: Verify column names in ON condition to avoid errors [OK]

Common Mistakes:

• Assuming aliases rename columns automatically
• Using wrong column names in ON clause
• Expecting empty result instead of error

5. You have two tables:

Orders
OrderID | CustomerID | Amount
1 | 101 | 50
2 | 102 | 75
3 | 103 | 100
4 | 101 | 25

Customers
CustomerID | Name
101 | John
102 | Jane
104 | Mike

Write an INNER JOIN query to find total order amount per customer name, including only customers with orders. Which query is correct?

hard

A. SELECT c.Name, SUM(o.Amount) FROM Customers c INNER JOIN Orders o ON c.CustomerID = o.CustomerID GROUP BY c.CustomerID;

B. SELECT c.Name, SUM(o.Amount) FROM Orders o INNER JOIN Customers c ON o.CustomerID = c.CustomerID GROUP BY c.Name;

C. SELECT c.Name, SUM(o.Amount) FROM Customers c LEFT JOIN Orders o ON c.CustomerID = o.CustomerID GROUP BY c.Name;

D. SELECT c.Name, SUM(o.Amount) FROM Orders o INNER JOIN Customers c ON o.CustomerID = c.CustomerID GROUP BY o.CustomerID;

Solution

1. Step 1: Understand requirement - total per customer with orders only

   INNER JOIN keeps only customers with matching orders; GROUP BY customer name to sum amounts.

2. Step 2: Check query correctness

   SELECT c.Name, SUM(o.Amount) FROM Orders o INNER JOIN Customers c ON o.CustomerID = c.CustomerID GROUP BY c.Name; joins Orders to Customers on CustomerID and groups by c.Name, matching requirement exactly.

3. Step 3: Compare other options

   SELECT c.Name, SUM(o.Amount) FROM Customers c INNER JOIN Orders o ON c.CustomerID = o.CustomerID GROUP BY c.CustomerID; groups by CustomerID but c.Name not grouped (SQL error). SELECT c.Name, SUM(o.Amount) FROM Customers c LEFT JOIN Orders o ON c.CustomerID = o.CustomerID GROUP BY c.Name; uses LEFT JOIN (includes customers without orders). SELECT c.Name, SUM(o.Amount) FROM Orders o INNER JOIN Customers c ON o.CustomerID = c.CustomerID GROUP BY o.CustomerID; groups by o.CustomerID (not customer name).

4. Final Answer:

   SELECT c.Name, SUM(o.Amount) FROM Orders o INNER JOIN Customers c ON o.CustomerID = c.CustomerID GROUP BY c.Name; -> Option B

5. Quick Check:

   INNER JOIN with GROUP BY customer name sums orders [OK]

Hint: Join Orders to Customers, group by customer name for totals [OK]

Common Mistakes:

• Using LEFT JOIN includes customers without orders
• Grouping by wrong column
• Joining tables in wrong order causing confusion