Joining more than two tables in SQL - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does it mean to join more than two tables in SQL?

Joining more than two tables means combining rows from three or more tables based on related columns to get a combined result set.

beginner

How do you join three tables in SQL?

You join three tables by writing multiple JOIN clauses, linking each table with the next using ON conditions that match related columns.

intermediate

Example: What does this SQL do?

SELECT * FROM A JOIN B ON A.id = B.a_id JOIN C ON B.id = C.b_id;

This query joins table A with B using A.id = B.a_id, then joins the result with C using B.id = C.b_id, combining data from all three tables.

intermediate

Why is the order of joins important when joining multiple tables?

The order affects how tables are combined and can impact performance and results, especially with different join types like INNER or LEFT JOIN.

beginner

Can you join more than three tables in SQL?

Yes, SQL allows joining many tables by chaining JOIN clauses, as long as each join has a valid ON condition linking tables.

What keyword is used to combine rows from multiple tables in SQL?

A CONNECT

B JOIN

C MERGE

D COMBINE

The JOIN keyword is used to combine rows from two or more tables based on related columns.

Which clause specifies how to match rows between tables when joining?

A GROUP BY

B WHERE

C ON

D HAVING

The ON clause defines the condition to match rows between tables in a JOIN.

If you want to join three tables A, B, and C, which is a correct SQL structure?

A SELECT * FROM A JOIN B JOIN C;

B SELECT * FROM A, B, C;

C SELECT * FROM A WHERE B JOIN C;

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

Option D correctly joins tables A to B and then B to C with ON conditions.

What happens if you omit the ON clause when joining tables?

A It performs a CROSS JOIN (cartesian product)

B SQL will throw an error

C It automatically matches columns with the same name

D It joins only the first row of each table

Without ON, JOIN defaults to CROSS JOIN, combining every row of one table with every row of the other.

Which join type keeps all rows from the first table even if no match is found in the second?

A LEFT JOIN

B INNER JOIN

C RIGHT JOIN

D FULL JOIN

LEFT JOIN keeps all rows from the left (first) table and matches rows from the right table if available.

Explain how to join three tables in SQL and why you need ON conditions.

Think about linking tables step by step using matching columns.

Describe what happens if you join tables without specifying ON conditions.

Consider what happens when no matching rule is given.

Practice

1. What is the main purpose of joining more than two tables in SQL?

easy

A. To combine related data from multiple tables into one result set

B. To delete data from multiple tables at once

C. To create new tables automatically

D. To backup tables in the database

Solution

1. Step 1: Understand the concept of JOIN

   JOIN is used to combine rows from two or more tables based on related columns.

2. Step 2: Apply to multiple tables

   Joining more than two tables extends this idea to combine data from several tables into one result.

3. Final Answer:

   To combine related data from multiple tables into one result set -> Option A

4. Quick Check:

   Joining multiple tables = combine data [OK]

Hint: Joining means combining data from tables step-by-step [OK]

Common Mistakes:

• Thinking JOIN deletes or creates tables
• Confusing JOIN with backup or delete operations
• Assuming JOIN works without conditions

2. Which of the following is the correct syntax to join three tables A, B, and C on columns A.id = B.a_id and B.id = C.b_id?

easy

A. SELECT * FROM A, B, C WHERE A.id = B.a_id, B.id = C.b_id;

B. SELECT * FROM A JOIN B ON A.id = B.a_id, C ON B.id = C.b_id;

C. SELECT * FROM A JOIN B JOIN C ON A.id = B.a_id AND B.id = C.b_id;

D. SELECT * FROM A JOIN B ON A.id = B.a_id JOIN C ON B.id = C.b_id;

Solution

1. Step 1: Check JOIN syntax for multiple tables

   Each JOIN must have its own ON condition to specify how tables connect.

2. Step 2: Validate SELECT * FROM A JOIN B ON A.id = B.a_id JOIN C ON B.id = C.b_id;

   SELECT * FROM A JOIN B ON A.id = B.a_id JOIN C ON B.id = C.b_id; correctly joins A to B with ON, then B to C with ON separately.

3. Final Answer:

   SELECT * FROM A JOIN B ON A.id = B.a_id JOIN C ON B.id = C.b_id; -> Option D

4. Quick Check:

   Each JOIN needs its own ON condition [OK]

Hint: Use separate ON for each JOIN clause [OK]

Common Mistakes:

• Combining multiple ON conditions in one JOIN
• Using commas with JOIN incorrectly
• Missing ON clause for a JOIN

3. Given tables:
Students(id, name),
Enrollments(student_id, course_id),
Courses(id, title)
What will the query below return?

SELECT Students.name, Courses.title FROM Students JOIN Enrollments ON Students.id = Enrollments.student_id JOIN Courses ON Enrollments.course_id = Courses.id;

medium

A. List of all students and all courses regardless of enrollment

B. List of student names with the titles of courses they are enrolled in

C. List of courses with no students enrolled

D. Syntax error due to missing WHERE clause

Solution

1. Step 1: Analyze JOINs in the query

   Students join Enrollments on student ID, then Enrollments join Courses on course ID, linking students to their courses.

2. Step 2: Understand SELECT output

   The query selects student names and course titles for matching enrollments, showing which student is in which course.

3. Final Answer:

   List of student names with the titles of courses they are enrolled in -> Option B

4. Quick Check:

   JOINs link students to their courses [OK]

Hint: JOIN chains link related data stepwise [OK]

Common Mistakes:

• Thinking JOIN returns all combinations without conditions
• Expecting courses without students to appear
• Assuming WHERE is required for JOIN

4. Identify the error in the following SQL query joining three tables:

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

medium

A. Missing WHERE clause for filtering

B. No error, query is correct

C. JOIN condition for table C should use B's columns, not A's

D. JOIN keyword is missing before table C

Solution

1. Step 1: Review JOIN conditions

   First JOIN connects A and B on A.id = B.a_id, which is correct.

2. Step 2: Check second JOIN condition

   Second JOIN connects C using A.id = C.a_id, but logically C should join via B, not A, to maintain correct relationships.

3. Final Answer:

   JOIN condition for table C should use B's columns, not A's -> Option C

4. Quick Check:

   JOIN conditions must link correct tables [OK]

Hint: Check JOIN ON uses correct table columns [OK]

Common Mistakes:

• Using wrong table columns in JOIN condition
• Assuming WHERE is needed for JOIN
• Ignoring logical table relationships

5. You have tables:
Orders(order_id, customer_id),
Customers(customer_id, name),
Payments(payment_id, order_id, amount).
Write a query to find each customer's name and the total amount they paid across all orders. Which query is correct?

hard

A. SELECT Customers.name, SUM(Payments.amount) FROM Customers JOIN Orders ON Customers.customer_id = Orders.customer_id JOIN Payments ON Orders.order_id = Payments.order_id GROUP BY Customers.name;

B. SELECT Customers.name, Payments.amount FROM Customers JOIN Orders ON Customers.customer_id = Orders.customer_id JOIN Payments ON Orders.order_id = Payments.order_id;

C. SELECT Customers.name, SUM(Payments.amount) FROM Customers, Orders, Payments WHERE Customers.customer_id = Orders.customer_id AND Orders.order_id = Payments.order_id;

D. SELECT Customers.name, SUM(Payments.amount) FROM Customers JOIN Payments ON Customers.customer_id = Payments.order_id GROUP BY Customers.name;

Solution

1. Step 1: Understand the relationships

   Customers link to Orders by customer_id; Orders link to Payments by order_id.

2. Step 2: Check aggregation and grouping

   We need total payment per customer, so SUM and GROUP BY Customers.name are required.

3. Step 3: Validate options

   SELECT Customers.name, SUM(Payments.amount) FROM Customers JOIN Orders ON Customers.customer_id = Orders.customer_id JOIN Payments ON Orders.order_id = Payments.order_id GROUP BY Customers.name; correctly joins tables and groups by customer name with SUM of payments. SELECT Customers.name, Payments.amount FROM Customers JOIN Orders ON Customers.customer_id = Orders.customer_id JOIN Payments ON Orders.order_id = Payments.order_id; lacks aggregation. SELECT Customers.name, SUM(Payments.amount) FROM Customers, Orders, Payments WHERE Customers.customer_id = Orders.customer_id AND Orders.order_id = Payments.order_id; misses GROUP BY. SELECT Customers.name, SUM(Payments.amount) FROM Customers JOIN Payments ON Customers.customer_id = Payments.order_id GROUP BY Customers.name; joins wrong columns.

4. Final Answer:

   SELECT Customers.name, SUM(Payments.amount) FROM Customers JOIN Orders ON Customers.customer_id = Orders.customer_id JOIN Payments ON Orders.order_id = Payments.order_id GROUP BY Customers.name; -> Option A

5. Quick Check:

   JOIN + SUM + GROUP BY = correct total per customer [OK]

Hint: Use JOINs with GROUP BY and SUM for totals [OK]

Common Mistakes:

• Missing GROUP BY when using SUM
• Joining tables on wrong columns
• Selecting aggregated and non-aggregated columns without GROUP BY