JOIN performance considerations in MySQL - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use indexes with JOINs?

When joining two large tables in MySQL, why is it important to have indexes on the join columns?

A Indexes automatically merge the tables before the join happens.

B Indexes speed up the search for matching rows, reducing the time to find join matches.

C Indexes prevent duplicate rows from appearing in the join result.

D Indexes compress the data to use less disk space during the join.

💡 Hint

Think about how the database finds matching rows quickly.

Indexes help the database quickly locate matching rows in join columns, making the join operation faster.

❓ query_result

intermediate

Result count of INNER JOIN with filtering

Given two tables, employees and departments, with 1000 and 10 rows respectively, and an INNER JOIN on department_id, what is the number of rows returned if only 5 departments have employees?

MySQL

SELECT e.employee_id, d.department_name FROM employees e INNER JOIN departments d ON e.department_id = d.department_id WHERE d.department_id IN (1,2,3,4,5);

A The number of employees in those 5 departments.

B Always 1000 rows because all employees are joined.

C 10 rows because there are 10 departments.

D 5 rows because only 5 departments are filtered.

💡 Hint

Think about how INNER JOIN and WHERE filter the rows.

The query returns all employees who belong to the 5 specified departments, so the count equals the number of employees in those departments.

📝 Syntax

advanced

Identify the correct JOIN syntax for performance optimization

Which of the following JOIN queries is syntactically correct and optimized for performance by using explicit JOIN syntax?

A SELECT * FROM orders INNER JOIN customers ON orders.customer_id = customers.id;

B SELECT * FROM orders LEFT JOIN customers USING (customer_id);

C SELECT * FROM orders, customers WHERE orders.customer_id = customers.id;

D SELECT * FROM orders JOIN customers WHERE orders.customer_id = customers.id;

💡 Hint

Look for the correct JOIN keyword and ON clause.

Option A uses explicit INNER JOIN with ON clause, which is clear and optimized for performance. Option A uses old implicit join syntax. Option A uses USING with a wrong column name. Option A misses ON clause.

❓ optimization

advanced

Best practice to reduce JOIN query time on large tables

You have two large tables joined on a column with no index. Which action will most improve the JOIN query performance?

A Increase the server's RAM without changing the query.

B Rewrite the query to use UNION instead of JOIN.

C Use SELECT * to fetch all columns for faster retrieval.

D Add an index on the join column in both tables.

💡 Hint

Think about how the database finds matching rows efficiently.

Adding indexes on join columns allows the database to quickly find matching rows, greatly improving join performance.

🔧 Debug

expert

Diagnose the cause of slow JOIN query

A JOIN query between two large tables runs very slowly. The query is:

SELECT a.id, b.name FROM table_a a JOIN table_b b ON a.ref_id = b.id WHERE b.status = 'active';

Which of the following is the most likely cause of the slow performance?

A The join condition uses <code>a.ref_id = b.id</code> which is invalid syntax.

B The WHERE clause filters on <code>b.status</code> but <code>b.id</code> is not indexed.

C Missing index on <code>b.status</code> column causing full scan after join.

D Using JOIN instead of LEFT JOIN causes slower execution.

💡 Hint

Consider which columns are filtered and joined and their indexes.

Without an index on b.status, the database must scan all rows after the join, slowing the query. Indexing b.status helps filter rows early.

Practice

1. Which factor most improves the performance of a JOIN operation in MySQL?

easy

A. Having indexes on the columns used in the JOIN condition

B. Using SELECT * to retrieve all columns

C. Joining tables without any WHERE clause

D. Using subqueries instead of JOINs

Solution

1. Step 1: Understand JOIN performance basics

   JOINs work faster when MySQL can quickly find matching rows using indexes on the join columns.

2. Step 2: Evaluate options for performance impact

   Using SELECT * or no WHERE clause does not improve speed; subqueries often perform worse than JOINs.

3. Final Answer:

   Having indexes on the columns used in the JOIN condition -> Option A

4. Quick Check:

   Indexes speed up JOINs = B [OK]

Hint: Indexes on join columns speed up JOINs [OK]

Common Mistakes:

• Thinking SELECT * is faster
• Ignoring the need for indexes
• Assuming subqueries are always faster

2. Which of the following is the correct syntax to perform an INNER JOIN between tables orders and customers on customer_id?

easy

A. SELECT * FROM orders JOIN customers ON orders.customer_id = customers.customer_id;

B. SELECT * FROM orders INNER JOIN customers WHERE orders.customer_id = customers.customer_id;

C. SELECT * FROM orders JOIN customers USING (customer_id);

D. SELECT * FROM orders, customers ON orders.customer_id = customers.customer_id;

Solution

1. Step 1: Review INNER JOIN syntax

   The correct INNER JOIN syntax uses JOIN ... ON condition, like in SELECT * FROM orders JOIN customers ON orders.customer_id = customers.customer_id;.

2. Step 2: Check other options for syntax errors

   SELECT * FROM orders INNER JOIN customers WHERE orders.customer_id = customers.customer_id; uses WHERE instead of ON, which is invalid for JOIN syntax. SELECT * FROM orders JOIN customers USING (customer_id); requires parentheses around the column name. SELECT * FROM orders, customers ON orders.customer_id = customers.customer_id; mixes comma join with ON, which is invalid.

3. Final Answer:

   SELECT * FROM orders JOIN customers ON orders.customer_id = customers.customer_id; -> Option A

4. Quick Check:

   JOIN ... ON is correct syntax = A [OK]

Hint: Use JOIN ... ON for correct INNER JOIN syntax [OK]

Common Mistakes:

• Using WHERE instead of ON for JOIN condition
• Mixing comma joins with ON clause
• Incorrect use of USING without parentheses

3. Given the tables:
employees(id, name, dept_id)
departments(id, dept_name)
and the query:

SELECT e.name, d.dept_name FROM employees e JOIN departments d ON e.dept_id = d.id WHERE d.dept_name = 'Sales';

What will be the result if there are 3 employees in 'Sales' department?

medium

A. Empty result because of missing GROUP BY

B. All employees regardless of department

C. Only department names without employee names

D. 3 rows with employee names and 'Sales' as dept_name

Solution

1. Step 1: Analyze the JOIN and WHERE clause

   The JOIN matches employees to departments by dept_id. The WHERE filters to only 'Sales' department.

2. Step 2: Determine output rows

   Since 3 employees belong to 'Sales', the query returns 3 rows with their names and 'Sales' as dept_name.

3. Final Answer:

   3 rows with employee names and 'Sales' as dept_name -> Option D

4. Quick Check:

   JOIN + WHERE filters = 3 matching rows [OK]

Hint: WHERE filters rows after JOIN, so only matching rows show [OK]

Common Mistakes:

• Assuming all employees are returned
• Expecting aggregation without GROUP BY
• Thinking only department names are returned

4. You wrote this query but it runs very slowly:

SELECT * FROM orders o JOIN customers c ON o.customer_id = c.id WHERE c.country = 'USA';

What is the most likely cause of poor performance?

medium

A. JOIN condition uses wrong columns

B. Using SELECT * instead of specific columns

C. Missing index on customers.country column

D. WHERE clause should be in the JOIN condition

Solution

1. Step 1: Identify performance bottleneck

   The WHERE clause filters by c.country = 'USA'. Without an index on country, MySQL scans all customers.

2. Step 2: Evaluate other options

   SELECT * does not cause slow JOINs. JOIN condition is correct. WHERE clause placement is valid.

3. Final Answer:

   Missing index on customers.country column -> Option C

4. Quick Check:

   Index missing on filter column = C [OK]

Hint: Index columns used in WHERE filters for faster JOINs [OK]

Common Mistakes:

• Blaming SELECT * for slow performance
• Misplacing WHERE clause inside JOIN
• Assuming JOIN condition is incorrect

5. You have two large tables: products (1 million rows) and sales (10 million rows). You want to find total sales per product. Which approach improves JOIN performance the most?

hard

A. Use a subquery to get sales totals, then join with products without indexes

B. Create indexes on sales.product_id and products.id, then use INNER JOIN with GROUP BY

C. Join without indexes and filter results in application code

D. Use CROSS JOIN and filter with WHERE clause

Solution

1. Step 1: Understand data size and join keys

   Large tables require indexes on join keys to avoid full scans and speed up matching.

2. Step 2: Evaluate join strategies

   INNER JOIN with proper indexes and GROUP BY efficiently aggregates sales per product. Subqueries without indexes or CROSS JOIN cause slow performance.

3. Final Answer:

   Create indexes on sales.product_id and products.id, then use INNER JOIN with GROUP BY -> Option B

4. Quick Check:

   Indexes + JOIN + GROUP BY = best performance [OK]

Hint: Index join keys and aggregate in SQL, not app [OK]

Common Mistakes:

• Skipping indexes on join columns
• Using CROSS JOIN causing huge intermediate results
• Filtering in application instead of SQL