How the join engine matches rows in SQL - Visual Walkthrough

Concept Flow - How the join engine matches rows

Start with Table A row

↓

Compare join key with Table B rows

↓

Match found?

No→Move to next Table B row

|Yes↓

Output combined row

↓

More Table B rows?

Yes→Compare next Table B row

|No↓

More Table A rows?

Yes→Next Table A row

|No↓

End

The join engine takes each row from the first table and compares its join key to each row in the second table. When keys match, it outputs the combined row. It repeats this until all rows are processed.

Execution Sample

SQL

SELECT * FROM A JOIN B ON A.id = B.id;

This query joins tables A and B by matching rows where the id column is the same.

Execution Table

Step	Current A row	Current B row	Join Key A.id	Join Key B.id	Match?	Action	Output Row
1	A1 (id=1)	B1 (id=1)	1	1	Yes	Output combined row	A1+B1
2	A1 (id=1)	B2 (id=2)	1	2	No	Skip
3	A2 (id=2)	B1 (id=1)	2	1	No	Skip
4	A2 (id=2)	B2 (id=2)	2	2	Yes	Output combined row	A2+B2
5	A3 (id=3)	B1 (id=1)	3	1	No	Skip
6	A3 (id=3)	B2 (id=2)	3	2	No	Skip
7	No more A rows					End

💡 All rows from Table A have been compared with all rows from Table B.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 4	After Step 7
Current A row	A1 (id=1)	A1 (id=1)	A2 (id=2)	A3 (id=3)	No more A rows
Current B row	B1 (id=1)	B2 (id=2)	B1 (id=1)	B1 (id=1)
Output Rows	[]	[A1+B1]	[A1+B1]	[A1+B1, A2+B2]	[A1+B1, A2+B2]

Key Moments - 2 Insights

Why does the join engine compare each row of Table A with every row of Table B?

Because the join needs to find all matching pairs based on the join key. As shown in execution_table rows 1-6, each A row is checked against all B rows to find matches.

What happens when the join keys do not match?

The engine skips outputting a combined row and moves to the next B row or A row. This is shown in execution_table rows 2, 3, 5, and 6 where no output is produced.

Visual Quiz - 3 Questions

Look at the execution_table, what is the output after step 4?

A Only the combined row A1+B1

B Combined rows A1+B1 and A2+B2

C No output yet

D Combined rows A1+B2 and A2+B1

💡 Hint

Check the 'Output Rows' variable in variable_tracker after step 4.

At which step does the join engine finish processing all rows?

A Step 4

B Step 6

C Step 7

D Step 1

💡 Hint

Look at the exit_note and the last row in execution_table.

If Table B had an extra row with id=3, what would happen at step 6?

A A3 would match with B3 and output a combined row

B No change, still no output at step 6

C The join would stop early

D A1 would match with B3

💡 Hint

Consider how the join engine compares each A row with all B rows as shown in execution_table.

Concept Snapshot

JOIN engine matches rows by:
- Taking each row from Table A
- Comparing its join key with every row in Table B
- Outputting combined rows when keys match
- Repeating until all rows are processed
This is how INNER JOIN works step-by-step.

Full Transcript

The join engine works by taking one row from the first table and comparing its join key to each row in the second table. If the keys match, it outputs a combined row with data from both tables. It repeats this process for every row in the first table until all rows have been checked. This step-by-step matching ensures all matching pairs are found and combined in the result.

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