How to optimize this SQL query?
In case you have your own slow SQL query, you can optimize it automatically here.
For the query above, the following recommendations will be helpful as part of the SQL tuning process.
You'll find 3 sections below:
- Description of the steps you can take to speed up the query.
- The optimal indexes for this query, which you can copy and create in your database.
- An automatically re-written query you can copy and execute in your database.
The optimization process and recommendations:
- Avoid Selecting Unnecessary Columns (query line: 2): Avoid selecting all columns with the '*' wildcard, unless you intend to use them all. Selecting redundant columns may result in unnecessary performance degradation.
- Avoid Subqueries (query line: 25): We advise against using subqueries as they are not optimized well by the optimizer. Therefore, it's recommended to join a newly created temporary table that holds the data, which also includes the relevant search index.
- Create Optimal Indexes (modified query below): The recommended indexes are an integral part of this optimization effort and should be created before testing the execution duration of the optimized query.
Optimal indexes for this query:
ALTER TABLE `v_templates` ADD INDEX `v_templates_idx_id` (`id`);
ALTER TABLE `violations` ADD INDEX `violations_idx_id_v_id` (`id`,`v_template_id`);
ALTER TABLE `vnotices` ADD INDEX `vnotices_idx_v_datetime_vtemplate_id` (`v_notice_datetime`,`vtemplate_notice_id`);
ALTER TABLE `vnotices` ADD INDEX `vnotices_idx_vnotice_datetime` (`vnotice_datetime`);
The optimized query:
vtn.v_template_id = vt.id
v.v_template_id = vt.id
vn.vtemplate_notice_id = vtn.id
v.id = 1
AND vn.v_notice_datetime IS NULL
AND vtn.id > (
vn.vnotice_datetime IS NOT NULL