You are a database expert and SQL optimizer. You will be given a SQL query and its…
- User
You are a database expert and SQL optimizer. You will be given a SQL query and its rewritten variant. The rewritten query improves performance upon the original while maintaining equivalence. Your task is to create a new pair of original and rewritten queries that invoke a similar rewrite.
[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 is similar to the provided demonstration.Keep the following points in mind while creating the new query pair:
- The original query must contain CTEs.
- The original query must make use of the following fact tables: ['store_sales', 'catalog_sales']. Below is the join graph for these fact tables: ['store_sales(ss_cdemo_sk) references customer_demographics(cd_demo_sk);', 'store_sales(ss_hdemo_sk) references household_demographics(hd_demo_sk);', 'store_sales(ss_sold_time_sk) references time_dim(t_time_sk);'] ['catalog_sales(cs_call_center_sk) references call_center(cc_call_center_sk);', 'catalog_sales(cs_ship_addr_sk) references customer_address(ca_address_sk);', 'catalog_sales(cs_sold_date_sk) references date_dim(d_date_sk);']
- The original query must employ 4 joins.
- The original query must employ the following aggregate functions: ['avg', 'count'].
- The original query must employ the following operators in its WHERE clause: ['sum', 'avg'].
- The rewritten query must be equivalent to the original query, and must follow a similar rewrite pattern as in the given example. Enclose the original and rewritten queries within
and.
- Assistant
Certainly! Below, I've constructed an original and a rewritten SQL query pair based on the given requirements and pattern.
[ORIGINAL QUERY]
with sales_info as ( select ss_item_sk, ss_quantity, ss_list_price, cd_marital_status from store_sales join customer_demographics on ss_cdemo_sk = cd_demo_sk join household_demographics on ss_hdemo_sk = hd_demo_sk where ss_sold_time_sk in (select t_time_sk from time_dim where t_hour between 9 and 17) ), catalog_info as ( select cs_item_sk, cs_quantity, cs_list_price, ca_city from catalog_sales join call_center on cs_call_center_sk = cc_call_center_sk join customer_address on cs_ship_addr_sk = ca_address_sk where cs_sold_date_sk in (select d_date_sk from date_dim where d_month = 'January') ) select case when (select count(*) from sales_info where ss_quantity > 5 and cd_marital_status = 'M') > 100 then (select avg(ss_list_price) from sales_info where ss_quantity > 5 and cd_marital_status = 'M') else (select avg(ss_list_price) from sales_info where cd_marital_status = 'S') end as high_quantity_married_sales, case when (select count(*) from catalog_info where cs_quantity > 2 and ca_city = 'New York') > 50 then (select avg(cs_list_price) from catalog_info where cs_quantity > 2 and ca_city = 'New York') else (select avg(cs_list_price) from catalog_info where ca_city = 'Los Angeles') end as high_quantity_ny_sales from sales_info, catalog_info where (select sum(ss_quantity) from sales_info) > 200 and (select avg(cs_list_price) from catalog_info) > 30;[REWRITTEN QUERY]
with sales_info as ( select ss_item_sk, ss_quantity, ss_list_price, cd_marital_status from store_sales join customer_demographics on ss_cdemo_sk = cd_demo_sk join household_demographics on ss_hdemo_sk = hd_demo_sk where ss_sold_time_sk in (select t_time_sk from time_dim where t_hour between 9 and 17) ), catalog_info as ( select cs_item_sk, cs_quantity, cs_list_price, ca_city from catalog_sales join call_center on cs_call_center_sk = cc_call_center_sk join customer_address on cs_ship_addr_sk = ca_address_sk where cs_sold_date_sk in (select d_date_sk from date_dim where d_month = 'January') ) select case when count(case when ss_quantity > 5 and cd_marital_status = 'M' then 1 end) > 100 then avg(case when ss_quantity > 5 and cd_marital_status = 'M' then ss_list_price end) else avg(case when cd_marital_status = 'S' then ss_list_price end) end as high_quantity_married_sales, case when count(case when cs_quantity > 2 and ca_city = 'New York' then 1 end) > 50 then avg(case when cs_quantity > 2 and ca_city = 'New York' then cs_list_price end) else avg(case when ca_city = 'Los Angeles' then cs_list_price end) end as high_quantity_ny_sales from sales_info join catalog_info on 1=1 where (select sum(ss_quantity) from sales_info) > 200 and (select avg(cs_list_price) from catalog_info) > 30;In the rewritten query, the subqueries inside the
CASEstatements have been eliminated by utilizing conditional aggregation. This is similar to the pattern demonstrated in the initial example, resulting in a potentially more efficient execution plan.