Subqueries vs JOINs comparison in MySQL - Performance Comparison

Time Complexity: Subqueries vs JOINs comparison

O(n x m)

Understanding Time Complexity

When we use subqueries or JOINs in SQL, the way the database processes data can change how long it takes to get results.

We want to understand how the time to run these queries grows as the data gets bigger.

Scenario Under Consideration

Analyze the time complexity of these two queries that find orders with customer details.

-- Using a subquery
SELECT order_id, customer_name
FROM orders
WHERE customer_id IN (
  SELECT customer_id FROM customers WHERE country = 'USA'
);

-- Using a JOIN
SELECT o.order_id, c.customer_name
FROM orders o
JOIN customers c ON o.customer_id = c.customer_id
WHERE c.country = 'USA';
    

Both queries get orders from customers in the USA but use different methods.

Identify Repeating Operations

Look at what repeats as data grows:

• Primary operation: Scanning and matching rows between orders and customers tables.
• How many times: For each order, the database checks matching customers (either via subquery or join).

How Execution Grows With Input

As the number of orders (n) and customers (m) grow, the work to find matches changes:

Input Size (orders n, customers m)	Approx. Operations
10, 10	About 100 checks
100, 100	About 10,000 checks
1000, 1000	About 1,000,000 checks

Pattern observation: The number of operations grows roughly with the product of the two table sizes.

Final Time Complexity

Time Complexity: O(n x m)

This means the time to run the query grows roughly with how many orders and customers there are multiplied together.

Common Mistake

[X] Wrong: "JOINs always run faster than subqueries because they look simpler."

[OK] Correct: Both can have similar time costs depending on indexes and data size; the database engine decides the best way to run them.

Interview Connect

Understanding how subqueries and JOINs scale helps you write efficient queries and explain your choices clearly in real projects and interviews.

Self-Check

What if we added an index on customer_id in both tables? How would the time complexity change?

Practice

1. Which of the following best describes the main difference between a JOIN and a subquery in MySQL?

easy

A. JOIN runs inside another query; subqueries combine tables side-by-side.

B. JOIN is used only for filtering; subqueries are used only for combining tables.

C. JOIN combines tables side-by-side; subqueries run inside another query to filter or find values.

D. JOIN and subqueries are exactly the same in functionality and performance.

Solution

1. Step 1: Understand the role of JOIN

   A JOIN combines rows from two or more tables side-by-side based on a related column between them.

2. Step 2: Understand the role of subqueries

   A subquery is a query nested inside another query, often used to filter or find specific values before the main query runs.

3. Final Answer:

   JOIN combines tables side-by-side; subqueries run inside another query to filter or find values. -> Option C

4. Quick Check:

   JOIN = combine tables, Subquery = nested query [OK]

Hint: JOINs combine tables; subqueries nest queries inside [OK]

Common Mistakes:

• Confusing JOINs as nested queries
• Thinking subqueries combine tables side-by-side
• Believing JOINs and subqueries have identical performance always

2. Which of the following is the correct syntax to write a JOIN between tables employees and departments on the column department_id?

easy

A. SELECT * FROM employees JOIN departments USING employees.department_id;

B. SELECT * FROM employees JOIN departments WHERE employees.department_id = departments.department_id;

C. SELECT * FROM employees, departments ON employees.department_id = departments.department_id;

D. SELECT * FROM employees JOIN departments ON employees.department_id = departments.department_id;

Solution

1. Step 1: Identify correct JOIN syntax

   The correct JOIN syntax uses the ON keyword to specify the matching columns between tables.

2. Step 2: Check each option

   SELECT * FROM employees JOIN departments ON employees.department_id = departments.department_id; uses ON correctly. SELECT * FROM employees JOIN departments WHERE employees.department_id = departments.department_id; incorrectly uses WHERE instead of ON. SELECT * FROM employees, departments ON employees.department_id = departments.department_id; uses comma join but incorrectly adds ON. SELECT * FROM employees JOIN departments USING employees.department_id; misuses USING with full column name.

3. Final Answer:

   SELECT * FROM employees JOIN departments ON employees.department_id = departments.department_id; -> Option D

4. Quick Check:

   JOIN requires ON for matching columns [OK]

Hint: Use ON to specify join condition, not WHERE [OK]

Common Mistakes:

• Using WHERE instead of ON for JOIN condition
• Using comma join with ON clause
• Incorrect USING syntax with full column names

3. Given the tables orders(order_id, customer_id, amount) and customers(customer_id, name), what will the following query return?

SELECT name FROM customers WHERE customer_id IN (SELECT customer_id FROM orders WHERE amount > 100);

medium

A. Names of customers who have orders with amount greater than 100.

B. All customer names regardless of orders.

C. Names of customers who have no orders.

D. Syntax error due to subquery.

Solution

1. Step 1: Analyze the subquery

   The subquery selects customer_id from orders where amount is greater than 100.

2. Step 2: Analyze the main query

   The main query selects names from customers where customer_id is in the list returned by the subquery.

3. Final Answer:

   Names of customers who have orders with amount greater than 100. -> Option A

4. Quick Check:

   Subquery filters customers by order amount [OK]

Hint: IN with subquery filters matching rows [OK]

Common Mistakes:

• Assuming all customers are returned
• Thinking it returns customers without orders
• Believing subquery causes syntax error

4. Identify the error in the following query that tries to list all employees with their department names:

SELECT e.name, d.department_name FROM employees e JOIN departments d WHERE e.department_id = d.department_id;

medium

A. Using WHERE instead of HAVING for join condition.

B. Missing ON keyword before the join condition.

C. Incorrect table aliases used.

D. No error; query is correct.

Solution

1. Step 1: Check JOIN syntax

   JOIN requires the ON keyword to specify the join condition between tables.

2. Step 2: Identify the mistake

   The query uses WHERE instead of ON to specify the join condition, which is incorrect syntax.

3. Final Answer:

   Missing ON keyword before the join condition. -> Option B

4. Quick Check:

   JOIN needs ON, not WHERE, for conditions [OK]

Hint: JOIN conditions must use ON, not WHERE [OK]

Common Mistakes:

• Using WHERE instead of ON for JOIN
• Confusing HAVING with JOIN condition
• Assuming aliases cause error

5. You want to find all customers who have placed orders but only want to use a JOIN instead of a subquery. Which query correctly replaces this subquery?

SELECT name FROM customers WHERE customer_id IN (SELECT customer_id FROM orders);

hard

A. SELECT DISTINCT c.name FROM customers c JOIN orders o ON c.customer_id = o.customer_id;

B. SELECT c.name FROM customers c JOIN orders o WHERE c.customer_id = o.customer_id;

C. SELECT c.name FROM customers c, orders o WHERE c.customer_id = o.customer_id;

D. SELECT name FROM customers LEFT JOIN orders ON customer_id = customer_id;

Solution

1. Step 1: Understand the original subquery

   The subquery selects customer_ids from orders, filtering customers who placed orders.

2. Step 2: Translate to JOIN

   Using JOIN on customer_id between customers and orders returns matching customers. DISTINCT is needed to avoid duplicates.

3. Step 3: Evaluate options

   SELECT DISTINCT c.name FROM customers c JOIN orders o ON c.customer_id = o.customer_id; uses JOIN with ON and DISTINCT correctly. SELECT c.name FROM customers c JOIN orders o WHERE c.customer_id = o.customer_id; misses ON keyword. SELECT c.name FROM customers c, orders o WHERE c.customer_id = o.customer_id; uses old-style join but is valid but may return duplicates. SELECT name FROM customers LEFT JOIN orders ON customer_id = customer_id; uses LEFT JOIN but ON condition is ambiguous.

4. Final Answer:

   SELECT DISTINCT c.name FROM customers c JOIN orders o ON c.customer_id = o.customer_id; -> Option A

5. Quick Check:

   JOIN with ON and DISTINCT matches subquery result [OK]

Hint: Use JOIN with ON and DISTINCT to replace IN subquery [OK]

Common Mistakes:

• Omitting ON keyword in JOIN
• Not using DISTINCT causing duplicates
• Using ambiguous ON conditions