What is the primary improvement that can be made for this scenario?

Consider the query: Mysql> SET @run = 15; Mysql> EXPLAIN SELECT objective, stage,
COUNT (stage) FROM iteminformation WHERE run=@run AND objective=’7.1’ GROUP BY
objective,stage ORDER BY stage; The iteminformation table has the following indexes;
Mysql> SHOW INDEXES FROM iteminformation: This query is run several times in an
application with different values in the WHERE clause in a growing data set. What is the
primary improvement that can be made for this scenario?

Consider the query: Mysql> SET @run = 15; Mysql> EXPLAIN SELECT objective, stage,
COUNT (stage) FROM iteminformation WHERE run=@run AND objective=’7.1’ GROUP BY
objective,stage ORDER BY stage; The iteminformation table has the following indexes;
Mysql> SHOW INDEXES FROM iteminformation: This query is run several times in an
application with different values in the WHERE clause in a growing data set. What is the
primary improvement that can be made for this scenario?

A.
Do not pass a user variable in the WHERE clause because it limits the ability of the
optimizer to use indexes.

B.
Add an index on the objective column so that is can be used in both the WHERE and
GROUP BY operations.

C.
Drop the run_2 index because it has caused a conflict in the choice of key for this query.

D.
Execute the run_2 index because it has caused a conflict in the choice of key for this
query.

E.
Add a composite index on (run,objective,stage) to allow the query to fully utilize an index.



Leave a Reply 3

Your email address will not be published. Required fields are marked *


Abel

Abel

E. Tested:
Creating an index on the objective column (Option D), the explain plan is the same:

create index o on i3(objective);

EXPLAIN SELECT objective, stage, COUNT(stage) FROM i3 WHERE run=@run AND objective=’7.1′ GROUP BY objective,stage;
+—-+————-+——-+——+—————+——+———+——-+——+————-+
| id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra |
+—-+————-+——-+——+—————+——+———+——-+——+————-+
| 1 | SIMPLE | i3 | ref | run,run2,o | run2 | 5 | const | 320 | Using where |
+—-+————-+——-+——+—————+——+———+——-+——+————-+

Creating the composite index, MySQL uses it:

create index comp on i3(run, objetive, stage);

EXPLAIN SELECT objective, stage, COUNT(stage) FROM i3 WHERE run=@run AND objective=’7.1′ GROUP BY objective,stage;
+—-+————-+——-+——+—————+——+———+————-+——+————————–+
| id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra |
+—-+————-+——-+——+—————+——+———+————-+——+————————–+
| 1 | SIMPLE | i3 | ref | run,run2,comp | comp | 28 | const,const | 64 | Using where; Using index |
+—-+————-+——-+——+—————+——+———+————-+——+————————–+