How the join engine matches rows in SQL - Quick Revision & Summary

Recall & Review

beginner

What is the main purpose of a join in SQL?

A join combines rows from two or more tables based on a related column between them.

beginner

How does the join engine find matching rows between tables?

It compares values in the join columns from each table to find pairs of rows where the values are equal (or meet the join condition).

intermediate

What is a nested loop join?

A nested loop join checks each row from one table against every row in the other table to find matches. It is simple but can be slow for large tables.

intermediate

What role do indexes play in join performance?

Indexes help the join engine quickly find matching rows by allowing fast lookups instead of scanning all rows.

advanced

Explain hash join in simple terms.

A hash join builds a fast lookup table (hash table) from one table’s join column, then checks each row in the other table against this hash table to find matches quickly.

What does a join engine compare to match rows?

A Values in the join columns

B Row numbers

C Table names

D Column data types

The join engine matches rows by comparing values in the columns specified in the join condition.

Which join method checks every row of one table against every row of another?

A Hash join

B Merge join

C Nested loop join

D Index join

Nested loop join compares each row from one table with all rows from the other table.

How do indexes help the join engine?

A By sorting the tables alphabetically

B By speeding up lookups for matching rows

C By increasing table size

D By changing data types

Indexes allow the join engine to find matching rows faster without scanning all rows.

What is the main advantage of a hash join?

A It builds a fast lookup table for quick matching

B It avoids comparing any rows

C It sorts tables alphabetically

D It uses less memory

Hash join creates a hash table from one table to quickly find matching rows from the other.

Which join type requires the join columns to be sorted?

A Cross join

B Hash join

C Nested loop join

D Merge join

Merge join requires both tables to be sorted on the join columns to efficiently match rows.

Describe how the join engine matches rows between two tables.

Think about how two lists can be matched by comparing their items.

Explain the difference between nested loop join and hash join.

One is simple but slow, the other uses a special table to speed up matching.

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