[Solved] Is there a possible way to optimize this union all sql?

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:

  1. Description of the steps you can take to speed up the query.
  2. The optimal indexes for this query, which you can copy and create in your database.
  3. An automatically re-written query you can copy and execute in your database.
The optimization process and recommendations:
  1. 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.
  2. Use Numeric Column Types For Numeric Values (query line: 7): Referencing a numeric value (e.g. 123) as a string in a WHERE clause might result in poor performance. Possible impacts of storing numbers as varchars: more space will be used, you won't be able to perform arithmetic operations, the data won't be self-validated, aggregation functions like SUM won't work, the output may sort incorrectly and more. If the column is numeric, remove the quotes from the constant value, to make sure a numeric comparison is done.
  3. Use Numeric Column Types For Numeric Values (query line: 8): Referencing a numeric value (e.g. 1) as a string in a WHERE clause might result in poor performance. Possible impacts of storing numbers as varchars: more space will be used, you won't be able to perform arithmetic operations, the data won't be self-validated, aggregation functions like SUM won't work, the output may sort incorrectly and more. If the column is numeric, remove the quotes from the constant value, to make sure a numeric comparison is done.
  4. Use Numeric Column Types For Numeric Values (query line: 16): Referencing a numeric value (e.g. 123) as a string in a WHERE clause might result in poor performance. Possible impacts of storing numbers as varchars: more space will be used, you won't be able to perform arithmetic operations, the data won't be self-validated, aggregation functions like SUM won't work, the output may sort incorrectly and more. If the column is numeric, remove the quotes from the constant value, to make sure a numeric comparison is done.
  5. Use Numeric Column Types For Numeric Values (query line: 17): Referencing a numeric value (e.g. 1) as a string in a WHERE clause might result in poor performance. Possible impacts of storing numbers as varchars: more space will be used, you won't be able to perform arithmetic operations, the data won't be self-validated, aggregation functions like SUM won't work, the output may sort incorrectly and more. If the column is numeric, remove the quotes from the constant value, to make sure a numeric comparison is done.
  6. Use Numeric Column Types For Numeric Values (query line: 27): Referencing a numeric value (e.g. 123) as a string in a WHERE clause might result in poor performance. Possible impacts of storing numbers as varchars: more space will be used, you won't be able to perform arithmetic operations, the data won't be self-validated, aggregation functions like SUM won't work, the output may sort incorrectly and more. If the column is numeric, remove the quotes from the constant value, to make sure a numeric comparison is done.
  7. Use Numeric Column Types For Numeric Values (query line: 28): Referencing a numeric value (e.g. 1) as a string in a WHERE clause might result in poor performance. Possible impacts of storing numbers as varchars: more space will be used, you won't be able to perform arithmetic operations, the data won't be self-validated, aggregation functions like SUM won't work, the output may sort incorrectly and more. If the column is numeric, remove the quotes from the constant value, to make sure a numeric comparison is done.
Optimal indexes for this query:
ALTER TABLE `chargetable` ADD INDEX `chargetable_idx_appid_status_ch_time` (`appid`,`status`,`ch_created_time`);
The optimized query:
SELECT
        SUM(`chargetable`.`amount`) AS total_amount,
        count(*) AS charge_count 
    FROM
        `chargetable` 
    WHERE
        `chargetable`.appid = '123' 
        AND `chargetable`.status = '1' 
    UNION
    ALL SELECT
        SUM(`chargetable`.`amount`) AS total_amount,
        count(*) AS charge_count 
    FROM
        `chargetable` 
    WHERE
        `chargetable`.appid = '123' 
        AND `chargetable`.status = '1' 
        AND `chargetable`.ch_created_time >= '2015-07-28 00:00:00' 
        AND `chargetable`.ch_created_time < '2015-07-28 01:00:00' 
    UNION
    ALL SELECT
        SUM(`chargetable`.`amount`) AS total_amount,
        count(*) AS charge_count 
    FROM
        `chargetable` 
    WHERE
        `chargetable`.appid = '123' 
        AND `chargetable`.status = '1' 
        AND `chargetable`.ch_created_time >= '2015-07-28 01:00:00' 
        AND `chargetable`.ch_created_time < '2015-07-28 02:00:00'

Related Articles



* original question posted on StackOverflow here.