Why indexes speed up queries in MySQL - Visual Breakdown

Concept Flow - Why indexes speed up queries

Start Query

↓

Check for Index

↓

Use Index

↓

Find Rows

↓

Return Result

↓

End

The database checks if an index exists for the query. If yes, it uses the index to find rows faster; if no, it scans the whole table.

Execution Sample

MySQL

SELECT * FROM users WHERE age = 30;
-- Assume 'age' column has an index

This query finds all users aged 30 using the index on the 'age' column to speed up search.

Execution Table

Step	Action	Index Used?	Rows Checked	Result
1	Start query execution	N/A	0	No rows yet
2	Check if 'age' column has index	Yes	0	Index found
3	Use index to find matching rows	Yes	Few (only matching age=30)	Rows found quickly
4	Return matching rows	Yes	Few	Result returned
5	End query	N/A	Few	Query complete

💡 Query ends after using index to quickly find matching rows instead of scanning whole table

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
Index Used	No	Yes	Yes	Yes	Yes
Rows Checked	0	0	Few (matching rows)	Few	Few
Rows Returned	0	0	Few	Few	Few

Key Moments - 2 Insights

Why does using an index check fewer rows than scanning the whole table?

Because the index stores sorted pointers to rows, the database can jump directly to matching rows instead of looking at every row (see execution_table step 3).

What happens if there is no index on the searched column?

The database must scan every row in the table to find matches, which is slower (see concept_flow path 'No' leading to 'Full Table Scan').

Visual Quiz - 3 Questions

Look at the execution_table, at which step does the database decide to use the index?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Check the 'Index Used?' column at each step in execution_table

According to variable_tracker, how many rows are checked after using the index?

A Few rows matching the condition

B All rows in the table

C No rows

D Exactly one row

💡 Hint

Look at 'Rows Checked' values after Step 3 in variable_tracker

If the 'age' column had no index, what would change in the execution flow?

A The database would still use the index

B The database would perform a full table scan

C The query would return no results

D The query would run faster

💡 Hint

Refer to concept_flow where 'No' index leads to 'Full Table Scan'

Concept Snapshot

Why indexes speed up queries:
- Indexes are like a book's index, pointing directly to data.
- Database checks for index before searching.
- Using index means fewer rows checked.
- Without index, full table scan is done.
- Indexes make queries faster by reducing search work.

Full Transcript

When a database runs a query, it first checks if there is an index on the column used in the search condition. If an index exists, the database uses it to quickly find matching rows without scanning the entire table. This is like using a book's index to find a topic instead of reading every page. The execution table shows the steps: starting the query, checking for an index, using the index to find rows, returning results, and ending the query. The variable tracker shows that after using the index, only a few rows are checked and returned. If no index exists, the database must scan every row, which is slower. Understanding this helps beginners see why indexes speed up queries.

Practice

1. Why do indexes speed up queries in MySQL?

easy

A. They store all data in memory for faster access.

B. They create shortcuts to quickly find data without scanning the whole table.

C. They compress the data to reduce size.

D. They automatically backup the database.

Solution

1. Step 1: Understand what an index does

   An index works like a shortcut or a map to find data quickly instead of checking every row.

2. Step 2: Compare with full table scan

   Without an index, MySQL must look at every row, which is slow for big tables.

3. Final Answer:

   They create shortcuts to quickly find data without scanning the whole table. -> Option B

4. Quick Check:

   Indexes = shortcuts to data [OK]

Hint: Think of index as a book's index for fast lookup [OK]

Common Mistakes:

• Confusing indexes with data compression
• Thinking indexes store all data in memory
• Believing indexes backup data automatically

2. Which of the following is the correct syntax to create an index on the column email in a table users?

easy

A. CREATE INDEX ON users email_index(email);

B. INDEX CREATE email_index ON users(email);

C. CREATE users INDEX email_index(email);

D. CREATE INDEX email_index ON users(email);

Solution

1. Step 1: Recall the correct CREATE INDEX syntax

   The correct syntax is: CREATE INDEX index_name ON table_name(column_name);

2. Step 2: Match syntax with options

   CREATE INDEX email_index ON users(email); matches the correct syntax exactly.

3. Final Answer:

   CREATE INDEX email_index ON users(email); -> Option D

4. Quick Check:

   CREATE INDEX index_name ON table(column) [OK]

Hint: Remember: CREATE INDEX name ON table(column) [OK]

Common Mistakes:

• Swapping keywords order
• Missing ON keyword
• Placing index name after table name incorrectly

3. Given the table products(id INT, name VARCHAR(50), price DECIMAL) with an index on price, what will be the effect of this query?
EXPLAIN SELECT * FROM products WHERE price = 100;

medium

A. The query will use the index on price to find matching rows quickly.

B. The query will scan the entire table ignoring the index.

C. The query will cause a syntax error due to missing index hint.

D. The query will lock the entire table during execution.

Solution

1. Step 1: Understand EXPLAIN output with index

   When a column has an index and the query filters on that column, MySQL uses the index to speed up search.

2. Step 2: Analyze query behavior

   The query filters by price = 100, so the index on price helps find rows without scanning all.

3. Final Answer:

   The query will use the index on price to find matching rows quickly. -> Option A

4. Quick Check:

   Index on filtered column = faster search [OK]

Hint: Filter on indexed column uses index automatically [OK]

Common Mistakes:

• Assuming index is ignored without hints
• Thinking syntax error occurs without hints
• Believing table locks always happen on SELECT

4. You created an index on column username but your query SELECT * FROM users WHERE username = 'alice'; is still slow. What could be the problem?

medium

A. The column username is not used in the WHERE clause.

B. The query syntax is incorrect and causes slow execution.

C. The index was not created properly or is corrupted.

D. Indexes slow down all queries by default.

Solution

1. Step 1: Check if index exists and is valid

   If the index was not created correctly or got corrupted, MySQL won't use it, causing slow queries.

2. Step 2: Verify query and column usage

   The query syntax is correct and uses the indexed column, so syntax or column usage is not the issue.

3. Final Answer:

   The index was not created properly or is corrupted. -> Option C

4. Quick Check:

   Index missing or broken = slow query [OK]

Hint: Check index existence if query is slow on indexed column [OK]

Common Mistakes:

• Blaming query syntax when it's correct
• Thinking indexes always slow queries
• Ignoring that column is used in WHERE clause

5. You have a large table orders with columns order_id, customer_id, and order_date. You often run this query:
SELECT * FROM orders WHERE customer_id = 123 AND order_date > '2023-01-01';
Which indexing strategy will speed up this query best?

hard

A. Create a composite index on (customer_id, order_date).

B. Create separate indexes on customer_id and order_date.

C. Create an index only on order_date.

D. No index is needed; full table scan is faster.

Solution

1. Step 1: Understand composite index benefits

   A composite index on (customer_id, order_date) helps MySQL filter rows by both columns efficiently in one index.

2. Step 2: Compare with separate indexes

   Separate indexes may be used but are less efficient than a composite index for combined conditions.

3. Final Answer:

   Create a composite index on (customer_id, order_date). -> Option A

4. Quick Check:

   Composite index matches multi-column WHERE best [OK]

Hint: Use composite index for multi-column WHERE filters [OK]

Common Mistakes:

• Creating only single-column indexes for multi-column queries
• Assuming full table scan is faster on large tables
• Ignoring order of columns in composite index