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 Calling Functions With Indexed Columns (query line: 7): When a function is used directly on an indexed column, the database's optimizer won’t be able to use the index. For example, if the column `invloc` is indexed, the index won’t be used as it’s wrapped with the function `WHMSLayer_IS_LOC_ACCESSIBLE`. If you can’t find an alternative condition that won’t use a function call, a possible solution is to store the required value in a new indexed column.
Avoid Optimizer Hints (modified query below): Using optimizer hints such as FORCE INDEX can be valuable in the short term. When important aspects such as the amount of data or the data distribution change, these hints can do more harm than good.
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 `inv` ADD INDEX `inv_idx_invsku` (`invsku`);
The optimized query:
inv.invsku >= 'PBM116-01'
AND WHMSLayer_IS_LOC_ACCESSIBLE('', 'PFCSYS ', inv.invloc) > 0