Query optimization strategies in DBMS Theory - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is query optimization in databases?

Query optimization is the process of improving the efficiency of a database query to reduce the time and resources needed to retrieve data.

beginner

Name one common strategy used in query optimization.

One common strategy is using indexes to quickly locate data without scanning the entire table.

intermediate

How does rewriting queries help in optimization?

Rewriting queries means changing the query structure to a more efficient form without changing its result, which helps the database run it faster.

intermediate

What role does the query execution plan play in optimization?

The query execution plan shows the steps the database will take to run a query. Optimizers choose the plan that uses the least resources.

advanced

Why is statistics collection important for query optimization?

Statistics provide information about data distribution and size, helping the optimizer make better decisions on how to run queries efficiently.

Which of the following is NOT a query optimization strategy?

A Query rewriting

B Increasing data redundancy

C Using indexes

D Collecting statistics

Increasing data redundancy is not a query optimization strategy; it can actually slow down queries.

What does a query execution plan help with?

A Showing how the database will execute a query

B Backing up the database

C Encrypting data

D Creating new tables

A query execution plan shows the steps the database will take to run a query.

Why are indexes useful in query optimization?

A They store backup copies of data

B They delete duplicate rows

C They speed up data retrieval by avoiding full table scans

D They compress data

Indexes help speed up data retrieval by allowing the database to find data quickly without scanning the whole table.

What is the purpose of collecting statistics in a database?

A To help the optimizer choose the best query plan

B To increase storage space

C To prevent data loss

D To create user accounts

Statistics help the optimizer understand data distribution and size to choose the best way to run queries.

Which action can improve query performance by changing the query without altering its result?

A Data deletion

B Backup scheduling

C Index dropping

D Query rewriting

Query rewriting changes the query structure to make it run faster while keeping the same results.

Explain the main strategies used in query optimization and why they are important.

Think about how databases find data faster and use less resources.

Describe how the query optimizer uses statistics to improve query performance.

Consider what information helps the optimizer pick the best way to run a query.

Practice

1. What is the main goal of query optimization in a database?

easy

A. To make data retrieval faster and more efficient

B. To increase the size of the database

C. To delete unnecessary data automatically

D. To encrypt data for security

Solution

1. Step 1: Understand the purpose of query optimization

   Query optimization aims to improve how quickly and efficiently data is retrieved from a database.

2. Step 2: Compare options with the goal

   Only To make data retrieval faster and more efficient matches this goal; others describe unrelated tasks.

3. Final Answer:

   To make data retrieval faster and more efficient -> Option A

4. Quick Check:

   Query optimization = faster data retrieval [OK]

Hint: Focus on speed and efficiency of data retrieval [OK]

Common Mistakes:

• Confusing optimization with data deletion
• Thinking optimization increases database size
• Mixing security tasks with optimization

2. Which of the following is a correct SQL syntax to create an index on the column employee_id in the table employees?

easy

A. CREATE employees INDEX idx_emp_id(employee_id);

B. MAKE INDEX idx_emp_id IN employees(employee_id);

C. INDEX CREATE idx_emp_id FOR employees(employee_id);

D. CREATE INDEX idx_emp_id ON employees(employee_id);

Solution

1. Step 1: Recall correct SQL syntax for creating an index

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

2. Step 2: Match options with correct syntax

   Only CREATE INDEX idx_emp_id ON employees(employee_id); matches the correct syntax exactly.

3. Final Answer:

   CREATE INDEX idx_emp_id ON employees(employee_id); -> Option D

4. Quick Check:

   CREATE INDEX ... ON ... (column) [OK]

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

Common Mistakes:

• Using wrong keywords like MAKE or FOR
• Placing table name before INDEX keyword
• Incorrect order of clauses

3. Consider the SQL query:
SELECT * FROM orders WHERE customer_id = 123;
If there is an index on customer_id, what is the expected effect on query performance?

medium

A. The query will return incorrect results

B. The query will run slower because indexes add overhead

C. The query will run faster by quickly locating matching rows

D. The query will ignore the index and scan the whole table

Solution

1. Step 1: Understand the role of indexes in queries

   Indexes help the database find rows matching conditions faster without scanning the entire table.

2. Step 2: Analyze the effect of an index on customer_id

   Since the query filters by customer_id, the index speeds up locating those rows.

3. Final Answer:

   The query will run faster by quickly locating matching rows -> Option C

4. Quick Check:

   Index on filter column = faster query [OK]

Hint: Index on filter column speeds up data retrieval [OK]

Common Mistakes:

• Thinking indexes slow down SELECT queries
• Assuming indexes cause wrong results
• Believing indexes are always ignored

4. A developer wrote this SQL query:
SELECT * FROM products WHERE price > 100 AND price < 50;
What is the main issue affecting query optimization here?

medium

A. The SELECT * syntax is invalid

B. The WHERE clause has conflicting conditions making the query return no rows

C. The query is missing an index on the price column

D. The table name is misspelled

Solution

1. Step 1: Analyze the WHERE clause conditions

   The conditions price > 100 and price < 50 cannot be true at the same time.

2. Step 2: Understand impact on query results and optimization

   This conflict means no rows will match, so the query returns empty results, wasting resources.

3. Final Answer:

   The WHERE clause has conflicting conditions making the query return no rows -> Option B

4. Quick Check:

   Conflicting WHERE conditions = no results [OK]

Hint: Check WHERE conditions for logical conflicts [OK]

Common Mistakes:

• Assuming SELECT * is wrong syntax
• Ignoring logical conflicts in conditions
• Thinking missing index causes no results

5. You have a large table sales with columns sale_date, region, and amount. You want to optimize this query:
SELECT region, SUM(amount) FROM sales WHERE sale_date BETWEEN '2023-01-01' AND '2023-01-31' GROUP BY region;
Which strategy will best improve performance?

hard

A. Create a composite index on (sale_date, region)

B. Create an index only on amount

C. Remove the GROUP BY clause

D. Use SELECT * instead of specific columns

Solution

1. Step 1: Identify columns used in WHERE and GROUP BY clauses

   The query filters by sale_date and groups by region.

2. Step 2: Choose an index that supports both filtering and grouping

   A composite index on (sale_date, region) helps quickly find rows in the date range and group them efficiently.

3. Final Answer:

   Create a composite index on (sale_date, region) -> Option A

4. Quick Check:

   Composite index on filter and group columns = better performance [OK]

Hint: Index columns used in WHERE and GROUP BY together [OK]

Common Mistakes:

• Indexing only the aggregated column
• Removing GROUP BY loses needed grouping
• Using SELECT * increases data load unnecessarily