Query optimization techniques in MySQL

Introduction

Query optimization helps your database find answers faster. It makes your searches quicker and saves computer power.

When your database queries take too long to finish.

When you want to reduce the load on your database server.

When you have many users accessing data at the same time.

When you want to improve the speed of reports or dashboards.

When you notice slow response times in your application.

Syntax

MySQL

No single syntax; optimization uses techniques like indexing, rewriting queries, and analyzing query plans.

Optimization is about improving how queries run, not a specific command.

Tools like EXPLAIN help understand query performance.

Examples

This creates an index on the 'name' column to speed up searches by name.

MySQL

CREATE INDEX idx_name ON employees(name);

Shows how MySQL plans to run this query, helping find slow parts.

MySQL

EXPLAIN SELECT * FROM employees WHERE name = 'Alice';

Using LIKE with a wildcard at the end can use indexes efficiently.

MySQL

SELECT name FROM employees WHERE name LIKE 'A%';

Using LIKE with a wildcard at the start cannot use indexes well and is slower.

MySQL

SELECT name FROM employees WHERE name LIKE '%A';

Sample Program

This example creates a table, adds some data, creates an index on the 'name' column, and then uses EXPLAIN to see how MySQL will run a search by name.

MySQL

CREATE TABLE employees (
  id INT PRIMARY KEY,
  name VARCHAR(100),
  department VARCHAR(50)
);

INSERT INTO employees (id, name, department) VALUES
(1, 'Alice', 'HR'),
(2, 'Bob', 'IT'),
(3, 'Charlie', 'Finance');

-- Create an index to speed up searches by name
CREATE INDEX idx_name ON employees(name);

-- Check the query plan
EXPLAIN SELECT * FROM employees WHERE name = 'Alice';

Important Notes

Indexes speed up searches but slow down inserts and updates slightly.

Use EXPLAIN to understand how your query runs and where to improve.

Rewrite queries to avoid unnecessary columns or rows.

Summary

Query optimization makes your database faster and more efficient.

Use indexes to speed up searches on columns you query often.

Check query plans with EXPLAIN to find slow parts.

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