EXPLAIN query analysis in MySQL - Mini Project: Build & Apply

Understanding EXPLAIN Query Analysis in MySQL

📖 Scenario: You are working with a small online bookstore database. You want to understand how MySQL runs your queries to make them faster and more efficient.

🎯 Goal: Learn how to use the EXPLAIN statement to analyze a SQL query and understand its execution plan.

📋 What You'll Learn

Create a simple table called books with columns id, title, and author.

Insert some sample data into the books table.

Write a SELECT query to find books by a specific author.

Use the EXPLAIN statement to analyze the SELECT query.

💡 Why This Matters

🌍 Real World

Database developers and administrators use EXPLAIN to understand and improve query performance in real applications.

💼 Career

Knowing how to analyze query execution plans is essential for optimizing databases and ensuring fast response times in software jobs.

1

Create the books table

Write a SQL statement to create a table called books with columns id as an integer primary key, title as a VARCHAR(100), and author as a VARCHAR(50).

MySQL

-- Your code here to create the books table

Hint

Use CREATE TABLE with the specified columns and types.

2

Insert sample data into books

Insert three rows into the books table with these exact values: (1, 'The Great Gatsby', 'F. Scott Fitzgerald'), (2, '1984', 'George Orwell'), and (3, 'To Kill a Mockingbird', 'Harper Lee').

MySQL

CREATE TABLE books (
  id INT PRIMARY KEY,
  title VARCHAR(100),
  author VARCHAR(50)
);
-- Your code here to insert data

Hint

Use a single INSERT INTO statement with multiple rows.

3

Write a SELECT query to find books by 'George Orwell'

Write a SQL SELECT statement to get all columns from books where the author is exactly 'George Orwell'.

MySQL

CREATE TABLE books (
  id INT PRIMARY KEY,
  title VARCHAR(100),
  author VARCHAR(50)
);

INSERT INTO books (id, title, author) VALUES
(1, 'The Great Gatsby', 'F. Scott Fitzgerald'),
(2, '1984', 'George Orwell'),
(3, 'To Kill a Mockingbird', 'Harper Lee');

-- Your code here to select books by George Orwell

Hint

Use SELECT * FROM books WHERE author = 'George Orwell'.

4

Use EXPLAIN to analyze the SELECT query

Write a SQL statement that uses EXPLAIN before the SELECT query to see how MySQL executes it. Use the exact query: EXPLAIN SELECT * FROM books WHERE author = 'George Orwell';

MySQL

CREATE TABLE books (
  id INT PRIMARY KEY,
  title VARCHAR(100),
  author VARCHAR(50)
);

INSERT INTO books (id, title, author) VALUES
(1, 'The Great Gatsby', 'F. Scott Fitzgerald'),
(2, '1984', 'George Orwell'),
(3, 'To Kill a Mockingbird', 'Harper Lee');

SELECT * FROM books WHERE author = 'George Orwell';

-- Your code here to add EXPLAIN before the SELECT query

Hint

Simply add EXPLAIN before the SELECT query.

Practice

1. What is the main purpose of using EXPLAIN before a SELECT query in MySQL?

easy

A. To create a backup of the database

B. To run the query faster by optimizing it automatically

C. To delete rows from the table before selecting

D. To see how MySQL plans to execute the query and find performance issues

Solution

1. Step 1: Understand the role of EXPLAIN

   EXPLAIN shows the execution plan MySQL uses for a query, helping to understand how tables and indexes are accessed.

2. Step 2: Identify what EXPLAIN does not do

   EXPLAIN does not run the query faster, delete data, or create backups; it only provides information about query execution.

3. Final Answer:

   To see how MySQL plans to execute the query and find performance issues -> Option D

4. Quick Check:

   EXPLAIN shows query plan = D [OK]

Hint: EXPLAIN shows query plan, not actual data changes [OK]

Common Mistakes:

• Thinking EXPLAIN runs the query faster
• Confusing EXPLAIN with data modification commands
• Assuming EXPLAIN creates backups

2. Which of the following is the correct syntax to use EXPLAIN with a SELECT query in MySQL?

easy

A. EXPLAIN * SELECT FROM users;

B. EXPLAIN SELECT * FROM users;

C. SELECT EXPLAIN * FROM users;

D. SELECT * FROM users EXPLAIN;

Solution

1. Step 1: Recall the correct EXPLAIN syntax

   The correct syntax is to write EXPLAIN before the SELECT statement: EXPLAIN SELECT ....

2. Step 2: Check each option

   EXPLAIN SELECT * FROM users; uses the correct syntax. Options A, B, and D place EXPLAIN incorrectly and will cause syntax errors.

3. Final Answer:

   EXPLAIN SELECT * FROM users; -> Option B

4. Quick Check:

   EXPLAIN before SELECT = C [OK]

Hint: Put EXPLAIN right before SELECT to check query plan [OK]

Common Mistakes:

• Placing EXPLAIN after SELECT or at the end
• Using EXPLAIN as a function inside SELECT
• Writing EXPLAIN in the wrong order

3. Given the table employees(id, name, department_id) with an index on department_id, what does the type column in EXPLAIN output usually show when the index is used?

medium

A. ALL

B. index

C. ref

D. const

Solution

1. Step 1: Understand EXPLAIN 'type' values

   The 'type' column shows how MySQL accesses rows. 'ALL' means full table scan, 'ref' means index lookup by reference, 'index' means full index scan, and 'const' means constant lookup.

2. Step 2: Identify index usage for a foreign key

   When searching by an indexed column like department_id, MySQL uses 'ref' to find matching rows efficiently.

3. Final Answer:

   ref -> Option C

4. Quick Check:

   Index lookup by reference = ref = B [OK]

Hint: 'ref' means index used for matching rows, not full scan [OK]

Common Mistakes:

• Confusing 'ALL' with index usage
• Thinking 'index' means index lookup by key
• Assuming 'const' applies to indexed foreign keys

4. You run EXPLAIN SELECT * FROM orders WHERE customer_id = 5; but notice the type column shows ALL. What is the most likely reason?

medium

A. There is no index on customer_id

B. The query syntax is incorrect

C. The table is empty

D. MySQL automatically ignores indexes

Solution

1. Step 1: Interpret 'ALL' in EXPLAIN output

   'ALL' means MySQL is scanning the entire table, which is slow and usually means no index is used.

2. Step 2: Identify cause of full table scan

   If the query filters by customer_id but no index exists on that column, MySQL must scan all rows.

3. Final Answer:

   There is no index on customer_id -> Option A

4. Quick Check:

   Full scan means missing index = A [OK]

Hint: 'ALL' means full scan, usually missing index on filter column [OK]

Common Mistakes:

• Assuming syntax error causes 'ALL'
• Thinking empty table causes 'ALL'
• Believing MySQL ignores indexes by default

5. You have a query joining products and categories tables on category_id. EXPLAIN shows type as ALL for products and ref for categories. What is the best way to improve performance?

hard

A. Add an index on products.category_id

B. Rewrite the query without JOIN

C. Add an index on categories.category_id

D. Use SELECT * instead of specific columns

Solution

1. Step 1: Analyze EXPLAIN output for join

   'ALL' on products means full scan; 'ref' on categories means index used there.

2. Step 2: Identify missing index

   Since products is scanned fully, adding an index on products.category_id helps MySQL find matching rows faster.

3. Step 3: Evaluate other options

   Rewriting query or adding index on categories.category_id won't help if products lacks index. SELECT * vs specific columns affects data size, not join efficiency.

4. Final Answer:

   Add an index on products.category_id -> Option A

5. Quick Check:

   Full scan means missing index on join column = A [OK]

Hint: Add index on table with 'ALL' type to speed up joins [OK]

Common Mistakes:

• Adding index on already indexed table
• Removing JOIN instead of indexing
• Ignoring EXPLAIN 'type' column meaning