You are a database expert and SQL optimizer. You will be given a SQL rewrite rule, an…
- User
You are a database expert and SQL optimizer. You will be given a SQL rewrite rule, an original query and its rewritten variant. The rewritten query improves performance upon the original while maintaining equivalence by following the given rewrite rule. Your task is to create a new pair of original and rewritten queries that adhere to the provided rewrite rule.
[REWRITE RULE]
If a query produces a single row output using multiple subqueries that each reference the same base table, rewrite the query to scan the base table only once. Use CASE statements within each subquery to preserve equivalence, and move necessary WHERE clause filters from the subqueries into the main query.[ORIGINAL QUERY]
select case when (select count(*) from store_sales where ss_quantity between 1 and 20) > 1071 then (select avg(ss_ext_tax) from store_sales where ss_quantity between 1 and 20) else (select avg(ss_net_paid_inc_tax) from store_sales where ss_quantity between 1 and 20) end bucket1,case when (select count(*) from store_sales where ss_quantity between 21 and 40) > 39161 then (select avg(ss_ext_tax) from store_sales where ss_quantity between 21 and 40) else (select avg(ss_net_paid_inc_tax) from store_sales where ss_quantity between 21 and 40) end bucket2,case when (select count(*) from store_sales where ss_quantity between 41 and 60) > 29434 then (select avg(ss_ext_tax) from store_sales where ss_quantity between 41 and 60) else (select avg(ss_net_paid_inc_tax) from store_sales where ss_quantity between 41 and 60) end bucket3,case when (select count(*) from store_sales where ss_quantity between 61 and 80) > 6568 then (select avg(ss_ext_tax) from store_sales where ss_quantity between 61 and 80) else (select avg(ss_net_paid_inc_tax) from store_sales where ss_quantity between 61 and 80) end bucket4,case when (select count(*) from store_sales where ss_quantity between 81 and 100) > 21216 then (select avg(ss_ext_tax) from store_sales where ss_quantity between 81 and 100) else (select avg(ss_net_paid_inc_tax) from store_sales where ss_quantity between 81 and 100) end bucket5 from reason where r_reason_sk = 1 ;[REWRITTEN QUERY]
select case when count(case when ss_quantity between 1 and 20 then 1 end) > 1071 then avg(case when ss_quantity between 1 and 20 then ss_ext_tax end) else avg(case when ss_quantity between 1 and 20 then ss_net_paid_inc_tax end) end as bucket1, case when count(case when ss_quantity between 21 and 40 then 1 end) > 39161 then avg(case when ss_quantity between 21 and 40 then ss_ext_tax end) else avg(case when ss_quantity between 21 and 40 then ss_net_paid_inc_tax end) end as bucket2, case when count(case when ss_quantity between 41 and 60 then 1 end) > 29434 then avg(case when ss_quantity between 41 and 60 then ss_ext_tax end) else avg(case when ss_quantity between 41 and 60 then ss_net_paid_inc_tax end) end as bucket3, case when count(case when ss_quantity between 61 and 80 then 1 end) > 6568 then avg(case when ss_quantity between 61 and 80 then ss_ext_tax end) else avg(case when ss_quantity between 61 and 80 then ss_net_paid_inc_tax end) end as bucket4, case when count(case when ss_quantity between 81 and 100 then 1 end) > 21216 then avg(case when ss_quantity between 81 and 100 then ss_ext_tax end) else avg(case when ss_quantity between 81 and 100 then ss_net_paid_inc_tax end) end as bucket5 from store_sales where exists (select 1 from reason where r_reason_sk = 1);[EXPLANATION] The rewritten query scans the employees table only once and uses CASE statements to conditionally calculate the average salary for each department. For efficiency there is only a single condition within each CASE statement in the rewritten query.
Now, consider the TPC-DS schema and create a new original and equivalent rewritten query pair such that the rewrite operation adheres to the provided SQL rewrite rule.Keep the following points in mind while creating the new query pair:
- The original query must make use of the following fact tables: ['store_returns']. Below is the join graph for these fact tables: ['store_returns(sr_addr_sk) references customer_address(ca_address_sk);', 'store_returns(sr_cdemo_sk) references customer_demographics(cd_demo_sk);', 'store_returns(sr_reason_sk) references reason(r_reason_sk);']
- The original query must employ 3 joins.
- The original query must employ the following aggregate functions: ['min', 'count', 'avg'].
- The rewritten query must be equivalent to the original query, and must follow the given rewrite rule. Enclose the original and rewritten queries within
and.
- Assistant
Here is a new pair of original and rewritten queries based on the outlined requirements:
[ORIGINAL QUERY]
select (select min(sr_return_amt) from store_returns where sr_reason_sk = r.r_reason_sk) as min_return_amount, (select count(*) from store_returns where sr_reason_sk = r.r_reason_sk) as total_returns, (select avg(sr_return_amt) from store_returns where sr_reason_sk = r.r_reason_sk) as avg_return_amount from reason r join customer_demographics cd on r.r_reason_sk = cd.cd_demo_sk join customer_address ca on cd.cd_demo_sk = ca.ca_address_sk where r.r_reason_sk is not null;[REWRITTEN QUERY]
select min(case when sr_reason_sk = r.r_reason_sk then sr_return_amt end) as min_return_amount, count(case when sr_reason_sk = r.r_reason_sk then 1 end) as total_returns, avg(case when sr_reason_sk = r.r_reason_sk then sr_return_amt end) as avg_return_amount from store_returns sr join reason r on sr.sr_reason_sk = r.r_reason_sk join customer_demographics cd on sr.sr_cdemo_sk = cd.cd_demo_sk join customer_address ca on cd.cd_demo_sk = ca.ca_address_sk where r.r_reason_sk is not null group by r.r_reason_sk;Explanation:
- The original query performs three separate subqueries on the
store_returnstable, each filtering bysr_reason_sk, which leads to multiple scans of the same table. - The rewritten query scans the
store_returnstable only once and usesCASEstatements within aggregate functions to calculate the minimum, count, and average return amount based on thesr_reason_sk. It ensures the same filtering logic is applied but efficiently combines the logic into a single scan.
- The original query performs three separate subqueries on the