Why joins are needed in SQL

Introduction

Joins help combine data from two or more tables to see related information together. This is useful because data is often stored in separate tables to keep it organized.

You want to see customer details along with their orders.

You need to find employees and the departments they work in.

You want to list products along with their supplier information.

You want to combine student records with their grades from different tables.

Syntax

SQL

SELECT columns
FROM table1
JOIN table2 ON table1.common_column = table2.common_column;

The JOIN keyword connects rows from two tables based on a related column.

The ON clause specifies the condition to match rows between tables.

Examples

This query shows customer names with their order IDs by joining Customers and Orders tables on CustomerID.

SQL

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

This query lists employees with their department names by joining Employees and Departments tables.

SQL

SELECT Employees.Name, Departments.DepartmentName
FROM Employees
JOIN Departments ON Employees.DepartmentID = Departments.DepartmentID;

Sample Program

This example creates two tables, Customers and Orders, inserts sample data, and then joins them to show each customer's products.

SQL

CREATE TABLE Customers (CustomerID INT, Name VARCHAR(50));
CREATE TABLE Orders (OrderID INT, CustomerID INT, Product VARCHAR(50));

INSERT INTO Customers VALUES (1, 'Alice'), (2, 'Bob');
INSERT INTO Orders VALUES (101, 1, 'Book'), (102, 2, 'Pen'), (103, 1, 'Notebook');

SELECT Customers.Name, Orders.Product
FROM Customers
JOIN Orders ON Customers.CustomerID = Orders.CustomerID
ORDER BY Customers.Name;

Important Notes

Without joins, you would have to look at each table separately and try to match data manually.

Joins make it easy to combine related data and answer questions that involve multiple tables.

Summary

Joins combine data from multiple tables based on related columns.

They help you see connected information in one result.

Joins are essential for working with organized, multi-table databases.

Practice

1. Why do we use JOIN in SQL when working with multiple tables?

easy

A. To combine related data from two or more tables into one result

B. To delete rows from a table

C. To create a new table

D. To change the data type of a column

Solution

1. Step 1: Understand the purpose of JOIN

   JOIN is used to bring together rows from different tables based on a related column.

2. Step 2: Identify the correct use case

   Deleting rows, creating tables, or changing data types are not done with JOIN.

3. Final Answer:

   To combine related data from two or more tables into one result -> Option A

4. Quick Check:

   JOIN combines tables = To combine related data from two or more tables into one result [OK]

Hint: JOIN merges tables on related columns to see connected data [OK]

Common Mistakes:

• Thinking JOIN deletes or modifies tables
• Confusing JOIN with CREATE or DELETE commands
• Assuming JOIN changes data types

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

easy

A. SELECT * FROM Employees WHERE DepartmentID = Departments.DepartmentID;

B. SELECT * FROM Employees JOIN Departments ON Employees.DepartmentID = Departments.DepartmentID;

C. SELECT * FROM Employees JOIN Departments USING (DepartmentID);

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

Solution

1. Step 1: Check the JOIN condition syntax

   The correct JOIN syntax uses ON with matching columns: Employees.DepartmentID = Departments.DepartmentID.

2. Step 2: Verify the options

   SELECT * FROM Employees JOIN Departments ON Employees.DepartmentID = Departments.DepartmentID; uses correct ON syntax with matching columns. SELECT * FROM Employees WHERE DepartmentID = Departments.DepartmentID; uses WHERE incorrectly. SELECT * FROM Employees JOIN Departments USING (DepartmentID); uses USING with correct parentheses. SELECT * FROM Employees JOIN Departments ON Employees.ID = Departments.ID; joins on wrong columns.

3. Final Answer:

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

4. Quick Check:

   JOIN with ON and matching columns = SELECT * FROM Employees JOIN Departments ON Employees.DepartmentID = Departments.DepartmentID; [OK]

Hint: Use JOIN ... ON table1.col = table2.col for correct syntax [OK]

Common Mistakes:

• Using WHERE instead of ON for JOIN condition
• Joining on wrong columns
• Misusing USING without parentheses

3. Given two tables:
Students(id, name)
Grades(student_id, grade)
What will this query return?

SELECT Students.name, Grades.grade FROM Students JOIN Grades ON Students.id = Grades.student_id;

medium

A. An error because of missing WHERE clause

B. All students with NULL grades included

C. Only grades without student names

D. A list of student names with their grades where student IDs match

Solution

1. Step 1: Understand INNER JOIN behavior

   JOIN without specifying LEFT or RIGHT is INNER JOIN, which returns rows with matching keys in both tables.

2. Step 2: Analyze the query result

   The query returns student names and grades only where Students.id matches Grades.student_id.

3. Final Answer:

   A list of student names with their grades where student IDs match -> Option D

4. Quick Check:

   INNER JOIN returns matching rows = A list of student names with their grades where student IDs match [OK]

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

Common Mistakes:

• Expecting all students even without grades
• Thinking JOIN returns unmatched rows
• Assuming WHERE is needed for JOIN condition

4. You wrote this query:

SELECT * FROM Orders JOIN Customers ON Orders.CustomerID = Customers.ID;

But it returns an error. What is the most likely cause?

medium

A. The column names in ON clause do not match actual table columns

B. JOIN keyword is not supported in SQL

C. Missing WHERE clause after JOIN

D. SELECT * cannot be used with JOIN

Solution

1. Step 1: Check column names in ON clause

   If column names Orders.CustomerID or Customers.ID do not exist, SQL throws an error.

2. Step 2: Verify other options

   JOIN is valid SQL keyword, WHERE is optional, and SELECT * works with JOIN.

3. Final Answer:

   The column names in ON clause do not match actual table columns -> Option A

4. Quick Check:

   Wrong column names cause JOIN errors = The column names in ON clause do not match actual table columns [OK]

Hint: Check column names in ON clause carefully to avoid errors [OK]

Common Mistakes:

• Assuming JOIN keyword is invalid
• Thinking WHERE is mandatory after JOIN
• Believing SELECT * cannot be used with JOIN

5. You have two tables:
Authors(author_id, name)
Books(book_id, title, author_id)
You want to list all authors and their books, including authors who have no books yet. Which SQL join should you use?

hard

A. INNER JOIN

B. RIGHT JOIN

C. LEFT JOIN

D. CROSS JOIN

Solution

1. Step 1: Understand the requirement

   We want all authors listed, even if they have no books. This means we keep all rows from Authors.

2. Step 2: Choose the correct JOIN type

   LEFT JOIN keeps all rows from the left table (Authors) and matches books if available, else NULL.

3. Step 3: Exclude other JOIN types

   INNER JOIN excludes authors without books, RIGHT JOIN keeps all books, CROSS JOIN creates all combinations.

4. Final Answer:

   LEFT JOIN -> Option C

5. Quick Check:

   LEFT JOIN keeps all left table rows = LEFT JOIN [OK]

Hint: Use LEFT JOIN to keep all rows from the first table [OK]

Common Mistakes:

• Using INNER JOIN and missing authors without books
• Confusing RIGHT JOIN with LEFT JOIN
• Using CROSS JOIN which multiplies rows