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);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', 'web_sales']. Below is the join graph for these fact tables: ['store_returns(sr_cdemo_sk) references customer_demographics(cd_demo_sk);', 'store_returns(sr_reason_sk) references reason(r_reason_sk);', 'store_returns(sr_return_time_sk) references time_dim(t_time_sk);'] ['web_sales(ws_bill_cdemo_sk) references customer_demographics(cd_demo_sk);', 'web_sales(ws_ship_date_sk) references date_dim(d_date_sk);', 'web_sales(ws_ship_hdemo_sk) references household_demographics(hd_demo_sk);']
- The original query must employ 4 joins.
- The original query must employ the following aggregate functions: ['avg', 'sum', 'min'].
- The original query must employ the following operators in its WHERE clause: ['sum'].
- 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 original and rewritten query pair that adheres to the provided rewrite rule, while satisfying the specified conditions:
[ORIGINAL QUERY]
SELECT (SELECT AVG(sr_return_amt) FROM store_returns sr WHERE sr_cdemo_sk IN (SELECT cd_demo_sk FROM customer_demographics WHERE cd_income BETWEEN 50000 AND 100000) ) AS avg_return_amt, (SELECT SUM(ws_sales_price) FROM web_sales ws WHERE ws_bill_cdemo_sk IN (SELECT cd_demo_sk FROM customer_demographics WHERE cd_income BETWEEN 50000 AND 100000) ) AS total_sales, (SELECT MIN(ws_order_date) FROM web_sales ws WHERE ws_ship_date_sk IN (SELECT d_date_sk FROM date_dim WHERE d_year = 2023) ) AS first_order_date FROM reason r WHERE r_reason_sk = 2;[REWRITTEN QUERY]
SELECT AVG(CASE WHEN sr_cdemo_sk IN (SELECT cd_demo_sk FROM customer_demographics WHERE cd_income BETWEEN 50000 AND 100000) THEN sr_return_amt END) AS avg_return_amt, SUM(CASE WHEN ws_bill_cdemo_sk IN (SELECT cd_demo_sk FROM customer_demographics WHERE cd_income BETWEEN 50000 AND 100000) THEN ws_sales_price ELSE 0 END) AS total_sales, MIN(CASE WHEN ws_ship_date_sk IN (SELECT d_date_sk FROM date_dim WHERE d_year = 2023) THEN ws_order_date END) AS first_order_date FROM store_returns sr JOIN reason r ON sr_reason_sk = r.r_reason_sk JOIN web_sales ws ON sr_cdemo_sk = ws.ws_bill_cdemo_sk JOIN customer_demographics cd ON ws.ws_bill_cdemo_sk = cd.cd_demo_sk WHERE r.r_reason_sk = 2;The rewritten query scans the relevant tables only once and uses CASE statements to capture the logic of the original subqueries while moving needed filters to the main query. This optimizes the execution by reducing unnecessary table scans.