How the join engine matches rows in SQL - Try It Yourself

How the Join Engine Matches Rows

📖 Scenario: You are working with two simple tables in a store database: customers and orders. You want to understand how the database combines rows from these tables when you ask for matching customer orders.

🎯 Goal: Build a SQL query step-by-step that shows how the join engine matches rows from customers and orders using a common column customer_id.

📋 What You'll Learn

Create a customers table with exact columns and data

Create an orders table with exact columns and data

Write a SQL query that joins customers and orders on customer_id

Select specific columns to show matched rows

💡 Why This Matters

🌍 Real World

Joining tables is a common task in databases to combine related information, like customers and their orders.

💼 Career

Understanding how joins work is essential for data analysts, backend developers, and anyone working with relational databases.

1

Create the customers table with data

Write SQL code to create a table called customers with columns customer_id (integer) and customer_name (text). Insert these exact rows: (1, 'Alice'), (2, 'Bob'), (3, 'Charlie').

SQL

-- Create the customers table and insert data
-- Your code here

Hint

Use CREATE TABLE to define columns and INSERT INTO to add rows.

2

Create the orders table with data

Write SQL code to create a table called orders with columns order_id (integer), customer_id (integer), and order_total (integer). Insert these exact rows: (101, 1, 250), (102, 2, 150), (103, 1, 300).

SQL

CREATE TABLE customers (
    customer_id INTEGER,
    customer_name TEXT
);

INSERT INTO customers (customer_id, customer_name) VALUES
(1, 'Alice'),
(2, 'Bob'),
(3, 'Charlie');

-- Create the orders table and insert data
-- Your code here

Hint

Define the orders table with three columns and insert the given rows.

3

Write a JOIN query to match customers with their orders

Write a SQL SELECT query that joins customers and orders on the customer_id column. Select customer_name and order_total from the joined tables.

SQL

CREATE TABLE customers (
    customer_id INTEGER,
    customer_name TEXT
);

INSERT INTO customers (customer_id, customer_name) VALUES
(1, 'Alice'),
(2, 'Bob'),
(3, 'Charlie');

CREATE TABLE orders (
    order_id INTEGER,
    customer_id INTEGER,
    order_total INTEGER
);

INSERT INTO orders (order_id, customer_id, order_total) VALUES
(101, 1, 250),
(102, 2, 150),
(103, 1, 300);

-- Write a SELECT query joining customers and orders on customer_id
-- Your code here

Hint

Use JOIN with ON to match rows where customer_id is the same.

4

Complete the query with an ORDER BY clause

Add an ORDER BY clause to the previous query to sort the results by customer_name in ascending order.

SQL

CREATE TABLE customers (
    customer_id INTEGER,
    customer_name TEXT
);

INSERT INTO customers (customer_id, customer_name) VALUES
(1, 'Alice'),
(2, 'Bob'),
(3, 'Charlie');

CREATE TABLE orders (
    order_id INTEGER,
    customer_id INTEGER,
    order_total INTEGER
);

INSERT INTO orders (order_id, customer_id, order_total) VALUES
(101, 1, 250),
(102, 2, 150),
(103, 1, 300);

SELECT customers.customer_name, orders.order_total
FROM customers
JOIN orders ON customers.customer_id = orders.customer_id
-- Add ORDER BY to sort by customer_name
-- Your code here

Hint

Use ORDER BY customers.customer_name ASC to sort results alphabetically by customer name.

Practice

1. What does the SQL JOIN engine use to match rows from two tables?

easy

A. The ON condition specifying matching columns

B. The order of rows in each table

C. The number of columns in each table

D. The table names only

Solution

1. Step 1: Understand the role of the ON condition

   The ON condition defines which columns from each table must have matching values for rows to join.

2. Step 2: Recognize what the join engine uses

   The join engine uses this condition to pair rows correctly, ignoring row order or table names alone.

3. Final Answer:

   The ON condition specifying matching columns -> Option A

4. Quick Check:

   Join engine matches rows using ON condition [OK]

Hint: Remember: JOIN matches rows using ON condition columns [OK]

Common Mistakes:

• Thinking row order affects join matching
• Assuming table names determine matches
• Confusing number of columns with matching criteria

2. Which of the following is the correct syntax to join two tables Employees and Departments on the column DeptID?

easy

A. SELECT * FROM Employees JOIN Departments WHERE Employees.DeptID = Departments.DeptID;

B. SELECT * FROM Employees JOIN Departments USING Employees.DeptID;

C. SELECT * FROM Employees, Departments ON Employees.DeptID = Departments.DeptID;

D. SELECT * FROM Employees JOIN Departments ON Employees.DeptID = Departments.DeptID;

Solution

1. Step 1: Identify correct JOIN syntax

   The correct JOIN syntax uses JOIN ... ON ... to specify the matching condition.

2. Step 2: Check each option

   SELECT * FROM Employees JOIN Departments ON Employees.DeptID = Departments.DeptID; uses JOIN ... ON correctly. SELECT * FROM Employees JOIN Departments WHERE Employees.DeptID = Departments.DeptID; wrongly uses WHERE instead of ON. SELECT * FROM Employees, Departments ON Employees.DeptID = Departments.DeptID; misuses ON with comma join. SELECT * FROM Employees JOIN Departments USING Employees.DeptID; misuses USING syntax with table prefix.

3. Final Answer:

   SELECT * FROM Employees JOIN Departments ON Employees.DeptID = Departments.DeptID; -> Option D

4. Quick Check:

   JOIN syntax requires ON condition [OK]

Hint: JOIN needs ON, not WHERE or comma with ON [OK]

Common Mistakes:

• Using WHERE instead of ON for join condition
• Mixing comma joins with ON clause
• Incorrect USING syntax with table prefixes

3. Given tables Orders and Customers with columns CustomerID, what will be the result of this query?

SELECT Orders.OrderID, Customers.Name FROM Orders JOIN Customers ON Orders.CustomerID = Customers.CustomerID;

Assuming Orders has 3 rows with CustomerIDs 1, 2, 4 and Customers has 2 rows with CustomerIDs 1, 2.

medium

A. 3 rows with OrderIDs 1, 2, 4 and matching customer names for IDs 1 and 2 only

B. 2 rows with OrderIDs 1 and 2 only, matching customer names

C. All 3 rows with customer names, including NULL for CustomerID 4

D. No rows because CustomerID 4 does not exist in Customers

Solution

1. Step 1: Understand INNER JOIN behavior

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

2. Step 2: Apply to given data

   Orders have CustomerIDs 1, 2, 4; Customers have 1, 2. Only CustomerIDs 1 and 2 match, so only those rows appear.

3. Final Answer:

   2 rows with OrderIDs 1 and 2 only, matching customer names -> Option B

4. Quick Check:

   INNER JOIN returns only matching rows [OK]

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

Common Mistakes:

• Expecting unmatched rows to appear with NULLs
• Confusing INNER JOIN with LEFT JOIN
• Assuming all rows from first table appear

4. You wrote this query but it returns fewer rows than expected:

SELECT * FROM Products JOIN Categories ON Products.CategoryID = Categories.ID;

What is the most likely cause?

medium

A. There are Products with CategoryID values not present in Categories

B. The query needs a WHERE clause to filter rows

C. The JOIN keyword is missing

D. The join condition column names are swapped

Solution

1. Step 1: Analyze INNER JOIN behavior

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

2. Step 2: Consider missing matches

   If some Products have CategoryID values not in Categories, those Products are excluded, reducing rows.

3. Final Answer:

   There are Products with CategoryID values not present in Categories -> Option A

4. Quick Check:

   Missing matches cause fewer rows in INNER JOIN [OK]

Hint: INNER JOIN excludes rows without matching keys [OK]

Common Mistakes:

• Thinking swapped column names cause fewer rows
• Assuming JOIN keyword missing causes fewer rows
• Believing WHERE clause is needed to fix join

5. You want to list all employees and their department names, but some employees have no department assigned. Which join type should you use to ensure all employees appear, even if their department is missing?

hard

A. RIGHT JOIN

B. INNER JOIN

C. LEFT JOIN

D. FULL JOIN

Solution

1. Step 1: Understand join types and their row inclusion

   INNER JOIN includes only matching rows; LEFT JOIN includes all rows from the left table and matches from right; RIGHT JOIN is opposite; FULL JOIN includes all rows from both.

2. Step 2: Apply to employees and departments

   To list all employees even if no department exists, use LEFT JOIN from Employees (left) to Departments (right).

3. Final Answer:

   LEFT JOIN -> Option C

4. Quick Check:

   LEFT JOIN keeps all left table rows [OK]

Hint: Use LEFT JOIN to keep all left table rows [OK]

Common Mistakes:

• Using INNER JOIN and missing employees without departments
• Confusing RIGHT JOIN with LEFT JOIN
• Assuming FULL JOIN is needed when LEFT JOIN suffices