EXPLAIN plan for query analysis in SQL - Step-by-Step Execution

Concept Flow - EXPLAIN plan for query analysis

Start: Query Submitted

↓

Parse Query

↓

Generate Execution Plan

↓

Show Plan Details

↓

Analyze Plan for Optimization

The EXPLAIN command takes a SQL query, parses it, creates a plan for how the database will run it, then shows this plan so you can understand and improve the query.

Execution Sample

SQL

EXPLAIN SELECT * FROM employees WHERE department = 'Sales';

This command shows how the database plans to find employees in the Sales department.

Execution Table

Step	Action	Details	Result
1	Parse Query	Check syntax and structure	Query is valid
2	Generate Plan	Decide scan type (e.g., full table scan or index scan)	Plan created with full table scan
3	Estimate Cost	Calculate cost and rows expected	Cost=100, Rows=50
4	Show Plan	Display plan steps	Output plan with scan type and filters
5	End	Plan ready for review	Execution plan displayed

💡 Plan generation completes after showing the execution steps and cost estimates.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
Query	Raw SQL text	Parsed query tree	Execution plan structure	Cost and row estimates added	Plan ready for display
Plan Details	None	None	Scan type: full table scan	Cost=100, Rows=50	Displayed to user

Key Moments - 2 Insights

Why does EXPLAIN show a full table scan instead of using an index?

Because the query condition or table statistics suggest scanning the whole table is cheaper; see execution_table step 2 where scan type is chosen.

What does the cost number in the plan mean?

It estimates how much work the database expects to do; lower cost means faster query. This is shown in execution_table step 3.

Visual Quiz - 3 Questions

Look at the execution_table, what is the action in step 3?

A Estimate Cost

B Show Plan

C Parse Query

D Generate Plan

💡 Hint

Check the 'Action' column in execution_table row with Step 3.

At which step does the plan get displayed to the user?

A Step 1

B Step 2

C Step 4

D Step 5

💡 Hint

Look for 'Show Plan' action in execution_table.

If the query had an index on department, which step would most likely change?

A Step 1: Parse Query

B Step 2: Generate Plan

C Step 3: Estimate Cost

D Step 5: End

💡 Hint

Scan type choice happens in step 2, see execution_table.

Concept Snapshot

EXPLAIN shows how the database plans to run a query.
It parses the query, creates a plan, estimates cost, and displays steps.
Use it to find slow parts and improve queries.
Key parts: scan type, cost, rows estimated.
Run: EXPLAIN SELECT ...

Full Transcript

The EXPLAIN plan command helps you see how a database will run your SQL query. When you run EXPLAIN with a query, the database first checks the query's syntax and structure. Then it creates an execution plan, deciding how to find the data, like whether to scan the whole table or use an index. It estimates the cost and number of rows it expects to process. Finally, it shows you this plan so you can understand and optimize your query. For example, if EXPLAIN shows a full table scan, it means the database thinks scanning all rows is cheaper than using an index. The cost number tells you how much work the database expects to do; lower is better. By reading the EXPLAIN output, you can find slow parts and improve your SQL queries.

Practice

1. What is the main purpose of using EXPLAIN before running a SQL query?

easy

A. To see how the database plans to execute the query

B. To delete data from the database

C. To create a new table

D. To insert new rows into a table

Solution

1. Step 1: Understand the role of EXPLAIN

   EXPLAIN shows the steps the database will take to run a query, like a map of the plan.

2. Step 2: Identify the correct purpose

   It helps find slow parts and optimize queries, not to modify data or structure.

3. Final Answer:

   To see how the database plans to execute the query -> Option A

4. Quick Check:

   EXPLAIN = query plan [OK]

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

Common Mistakes:

• Thinking EXPLAIN modifies data
• Confusing EXPLAIN with data manipulation commands
• Assuming EXPLAIN creates or deletes tables

2. Which of the following is the correct syntax to get the execution plan of a query in SQL?

easy

A. EXPLAIN SELECT * FROM users;

B. PLAN EXPLAIN SELECT * FROM users;

C. SHOW PLAN FOR SELECT * FROM users;

D. RUN EXPLAIN ON SELECT * FROM users;

Solution

1. Step 1: Recall standard EXPLAIN syntax

   The standard way to get a query plan is to put EXPLAIN before the query.

2. Step 2: Check each option

   Only EXPLAIN SELECT * FROM users; uses the correct syntax: EXPLAIN SELECT ...; others are invalid or non-standard.

3. Final Answer:

   EXPLAIN SELECT * FROM users; -> Option A

4. Quick Check:

   EXPLAIN + query = correct syntax [OK]

Hint: Put EXPLAIN before the query to see the plan [OK]

Common Mistakes:

• Adding extra keywords like PLAN or RUN
• Using SHOW PLAN which is not standard SQL
• Placing EXPLAIN after the query

3. Given the query SELECT * FROM orders WHERE customer_id = 5;, what does the EXPLAIN plan typically show?

medium

A. The syntax errors in the query

B. The total number of rows in the orders table

C. The list of all customers in the database

D. The steps to scan the orders table and filter rows where customer_id = 5

Solution

1. Step 1: Understand what EXPLAIN outputs

   EXPLAIN shows how the database will find rows, like scanning and filtering steps.

2. Step 2: Match the query with the plan description

   The query filters orders by customer_id = 5, so the plan shows scanning and filtering those rows.

3. Final Answer:

   The steps to scan the orders table and filter rows where customer_id = 5 -> Option D

4. Quick Check:

   EXPLAIN = scan + filter steps [OK]

Hint: EXPLAIN shows how rows are found and filtered [OK]

Common Mistakes:

• Thinking EXPLAIN shows data counts
• Expecting EXPLAIN to list unrelated tables
• Confusing EXPLAIN output with errors

4. You run EXPLAIN SELECT name FROM employees WHERE age > 30; but get an error. What is the most likely cause?

medium

A. The EXPLAIN keyword is not supported in your SQL dialect

B. The query is missing a semicolon at the end

C. The table employees does not exist

D. The WHERE clause uses an invalid operator

Solution

1. Step 1: Check common EXPLAIN errors

   EXPLAIN syntax is usually supported; missing semicolon rarely causes errors in many tools.

2. Step 2: Consider table existence

   If the table does not exist, EXPLAIN cannot analyze the query and will error.

3. Final Answer:

   The table employees does not exist -> Option C

4. Quick Check:

   Missing table = EXPLAIN error [OK]

Hint: Check if tables exist before EXPLAIN [OK]

Common Mistakes:

• Assuming EXPLAIN is unsupported
• Blaming missing semicolon
• Thinking WHERE operator is invalid

5. You want to optimize a slow query joining two large tables. How can using EXPLAIN help you improve performance?

hard

A. By deleting duplicate rows from the tables

B. By showing which table is scanned first and if indexes are used

C. By automatically rewriting the query for better speed

D. By increasing the database server memory

Solution

1. Step 1: Understand EXPLAIN's role in optimization

   EXPLAIN shows the order of table scans and whether indexes help speed up lookups.

2. Step 2: Identify how this helps optimization

   Knowing scan order and index use helps rewrite queries or add indexes to improve speed.

3. Final Answer:

   By showing which table is scanned first and if indexes are used -> Option B

4. Quick Check:

   EXPLAIN reveals scan order and index use [OK]

Hint: EXPLAIN reveals scan order and index usage [OK]

Common Mistakes:

• Expecting EXPLAIN to fix queries automatically
• Confusing EXPLAIN with data cleanup
• Thinking EXPLAIN changes server settings