Query optimization techniques in MySQL - Step-by-Step Execution

Concept Flow - Query optimization techniques

Write SQL Query

↓

Parse Query

↓

Generate Query Plan

↓

Apply Optimization Techniques

↓

Choose Best Execution Plan

↓

Execute Query

↓

Return Results

The database takes your SQL query, parses it, creates a plan, applies optimizations to make it faster, chooses the best plan, then runs the query and returns the results.

Execution Sample

MySQL

SELECT * FROM employees WHERE department_id = 5;
-- Using index on department_id
-- Optimized query plan chosen

This query fetches all employees in department 5. The optimizer uses an index on department_id to speed up the search.

Execution Table

Step	Action	Details	Effect
1	Parse Query	Read SQL and check syntax	Query is valid
2	Generate Query Plan	Create possible ways to run query	Multiple plans created
3	Apply Optimization	Use index on department_id	Faster data access
4	Choose Best Plan	Select plan with lowest cost	Plan with index chosen
5	Execute Query	Run chosen plan	Rows with department_id=5 fetched
6	Return Results	Send data to user	Results displayed

💡 Query executed with optimized plan using index on department_id

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
Query Plan Options	None	Multiple plans generated	Plans optimized with indexes	Best plan selected	Best plan executed
Execution Cost	Unknown	Estimated for each plan	Reduced by optimization	Lowest cost chosen	Cost realized during execution

Key Moments - 3 Insights

Why does the optimizer choose to use an index instead of scanning the whole table?

Because using the index reduces the number of rows to check, making the query faster. This is shown in execution_table step 3 where optimization applies the index.

What happens if no index exists for the searched column?

The optimizer will choose a full table scan, which is slower. This is implied in execution_table step 3 where no index would mean no optimization applied.

How does the optimizer decide which plan is best?

It estimates the cost (time and resources) for each plan and picks the one with the lowest cost, as shown in execution_table step 4.

Visual Quiz - 3 Questions

Look at the execution_table, at which step does the optimizer apply the index?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Check the 'Action' and 'Details' columns in execution_table row for step 3.

According to variable_tracker, what happens to 'Execution Cost' after optimization?

A It increases

B It stays the same

C It is reduced

D It becomes unknown

💡 Hint

Look at the 'Execution Cost' row values from 'After Step 2' to 'After Step 3' in variable_tracker.

If the index on department_id was missing, which step in execution_table would change?

A Step 3

B Step 1

C Step 5

D Step 6

💡 Hint

Step 3 is where optimization applies indexes; without an index, this step would differ.

Concept Snapshot

Query Optimization Techniques:
- Database parses SQL query
- Generates multiple query plans
- Applies optimizations like indexes
- Chooses plan with lowest cost
- Executes optimized plan
- Returns results faster

Full Transcript

Query optimization is the process where the database takes your SQL query, checks it, and figures out the best way to run it quickly. It creates different plans to get the data, then uses tricks like indexes to speed up searching. The optimizer picks the fastest plan and runs it, returning your results efficiently. This process helps avoid slow full table scans and makes your queries faster.

Practice

1. What is the main purpose of using indexes in MySQL query optimization?

easy

A. To encrypt the data for security

B. To speed up data retrieval by reducing the search area

C. To store backup copies of data

D. To increase the size of the database

Solution

1. Step 1: Understand what indexes do

   Indexes help the database find rows faster by creating a quick lookup structure.

2. Step 2: Relate indexes to query speed

   By reducing the number of rows scanned, indexes speed up data retrieval significantly.

3. Final Answer:

   To speed up data retrieval by reducing the search area -> Option B

4. Quick Check:

   Indexes improve search speed = D [OK]

Hint: Indexes speed up searches by narrowing data to scan [OK]

Common Mistakes:

• Thinking indexes increase database size only
• Confusing indexes with backups
• Believing indexes encrypt data

2. Which of the following is the correct syntax to check the query execution plan in MySQL?

easy

A. EXPLAIN SELECT * FROM users;

B. PLAN SELECT * FROM users;

C. SHOW PLAN SELECT * FROM users;

D. DESCRIBE PLAN SELECT * FROM users;

Solution

1. Step 1: Recall the command to view query plans

   MySQL uses the EXPLAIN keyword before a SELECT query to show the execution plan.

2. Step 2: Identify the correct syntax

   Only EXPLAIN SELECT * FROM users; is valid syntax to check the plan.

3. Final Answer:

   EXPLAIN SELECT * FROM users; -> Option A

4. Quick Check:

   EXPLAIN shows query plan = C [OK]

Hint: Use EXPLAIN before SELECT to see query plan [OK]

Common Mistakes:

• Using SHOW PLAN which is invalid in MySQL
• Forgetting EXPLAIN keyword
• Confusing DESCRIBE with EXPLAIN

3. Given the table employees(id INT PRIMARY KEY, name VARCHAR(50), department_id INT) with an index on department_id, what will be the effect of this query?
SELECT * FROM employees WHERE department_id = 5;

medium

A. The query will scan the entire table without using the index

B. The query will return no rows because indexes filter data

C. The query will fail due to missing index

D. The query will use the index to quickly find rows with department_id = 5

Solution

1. Step 1: Understand index usage on department_id

   Since there is an index on department_id, MySQL can use it to locate matching rows efficiently.

2. Step 2: Analyze query behavior

   The WHERE clause filters by department_id = 5, so the index helps avoid scanning all rows.

3. Final Answer:

   The query will use the index to quickly find rows with department_id = 5 -> Option D

4. Quick Check:

   Index on filter column speeds query = B [OK]

Hint: Indexed columns in WHERE speed up searches [OK]

Common Mistakes:

• Assuming index is ignored automatically
• Thinking query fails without index
• Believing indexes filter out rows

4. You wrote this query:
SELECT * FROM orders WHERE customer_id = 10 AND status = 'shipped';
You notice it runs slowly. Which fix will most likely improve performance?

medium

A. Add ORDER BY customer_id

B. Remove the WHERE clause

C. Add an index on (customer_id, status)

D. Use SELECT COUNT(*) instead of SELECT *

Solution

1. Step 1: Identify slow query cause

   The query filters on two columns but may lack a composite index to speed filtering.

2. Step 2: Apply composite index for optimization

   Adding an index on (customer_id, status) helps MySQL quickly find matching rows using both filters.

3. Final Answer:

   Add an index on (customer_id, status) -> Option C

4. Quick Check:

   Composite index speeds multi-column filters = A [OK]

Hint: Use composite index for multiple WHERE columns [OK]

Common Mistakes:

• Removing WHERE clause loses filtering
• ORDER BY does not speed filtering
• Changing SELECT * to COUNT(*) changes result, not speed

5. You have a large table sales(date DATE, product_id INT, amount DECIMAL) without indexes. You want to find total sales for product 101 in 2023 quickly. Which optimization technique is best?

hard

A. Create an index on (product_id, date) and use a query filtering both

B. Add a full table scan hint to force scanning all rows

C. Use SELECT * without WHERE to get all data

D. Drop the table and recreate it

Solution

1. Step 1: Identify query needs

   The query filters by product_id and date range, so indexing these columns helps speed filtering.

2. Step 2: Apply composite index for efficient filtering

   Creating an index on (product_id, date) allows MySQL to quickly find relevant rows without scanning the whole table.

3. Final Answer:

   Create an index on (product_id, date) and use a query filtering both -> Option A

4. Quick Check:

   Composite index on filter columns = A [OK]

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

Common Mistakes:

• Forcing full table scan slows query
• Selecting all rows wastes time
• Dropping table loses data