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]
with customer_total_return as (select sr_customer_sk as ctr_customer_sk,sr_store_sk as ctr_store_sk,sum(SR_FEE) as ctr_total_return from store_returns,date_dim where sr_returned_date_sk = d_date_sk and d_year =2000 group by sr_customer_sk,sr_store_sk) select c_customer_id from customer_total_return ctr1,store,customer where ctr1.ctr_total_return > (select avg(ctr_total_return)*1.2 from customer_total_return ctr2 where ctr1.ctr_store_sk = ctr2.ctr_store_sk) and s_store_sk = ctr1.ctr_store_sk and s_state = 'TN' and ctr1.ctr_customer_sk = c_customer_sk order by c_customer_id limit 100;[REWRITTEN QUERY]
with customer_total_return as ( select sr_customer_sk as ctr_customer_sk, sr_store_sk as ctr_store_sk, sum(SR_FEE) as ctr_total_return from store_returns join date_dim on sr_returned_date_sk = d_date_sk where d_year = 2000 group by sr_customer_sk , sr_store_sk ), avg_customer_return as ( select ctr_store_sk, avg(ctr_total_return) as avg_return from customer_total_return group by ctr_store_sk ) select c_customer_id from customer_total_return ctr1 join store on s_store_sk = ctr1.ctr_store_sk join customer on ctr1.ctr_customer_sk = c_customer_sk join avg_customer_return acr on ctr1.ctr_store_sk = acr.ctr_store_sk where ctr1.ctr_total_return > acr.avg_return * 1.2 and s_state = 'TN' order by c_customer_id limit 100;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']. Below is the join graph for these fact tables: ['store_sales(ss_cdemo_sk) references customer_demographics(cd_demo_sk);', 'store_sales(ss_customer_sk) references customer(c_customer_sk);', 'store_sales(ss_store_sk) references store(s_store_sk);']
- The original query must employ 2 joins.
- The original query must employ the following aggregate functions: ['avg'].
- The original query must employ the following operators in its WHERE clause: ['avg', 'sum', 'min'].
- 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 is a new pair of SQL queries crafted following your specified requirements, which utilize the TPC-DS schema and exhibit a similar rewrite pattern as demonstrated in the provided example:
[ORIGINAL QUERY]
with sales_total_discount as ( select ss_customer_sk as std_customer_sk, ss_store_sk as std_store_sk, sum(ss_ext_discount_amt) as std_total_discount from store_sales, store where ss_store_sk = s_store_sk group by ss_customer_sk, ss_store_sk having std_total_discount > (select avg(std_total_discount) from (select ss_store_sk, sum(ss_ext_discount_amt) as std_total_discount from store_sales group by ss_store_sk) as subquery) ), min_max_sales as ( select ss_store_sk as minmax_store_sk, min(ss_ext_sales_price) as min_sales, max(ss_ext_sales_price) as max_sales from store_sales group by ss_store_sk ) select c_customer_id, mm.min_sales from sales_total_discount std, min_max_sales mm, customer where std.std_store_sk = mm.minmax_store_sk and std.std_customer_sk = c_customer_sk order by c_customer_id limit 50;[REWRITTEN QUERY]
with sales_total_discount as ( select ss_customer_sk as std_customer_sk, ss_store_sk as std_store_sk, sum(ss_ext_discount_amt) as std_total_discount from store_sales join store on ss_store_sk = s_store_sk group by ss_customer_sk, ss_store_sk ), avg_discount as ( select ss_store_sk, avg(std_total_discount) as avg_discount from (select ss_store_sk, sum(ss_ext_discount_amt) as std_total_discount from store_sales group by ss_store_sk) as subquery group by ss_store_sk ), min_max_sales as ( select ss_store_sk as minmax_store_sk, min(ss_ext_sales_price) as min_sales, max(ss_ext_sales_price) as max_sales from store_sales group by ss_store_sk ) select c_customer_id, mm.min_sales from sales_total_discount std join avg_discount ad on std.std_store_sk = ad.ss_store_sk join min_max_sales mm on std.std_store_sk = mm.minmax_store_sk join customer on std.std_customer_sk = c_customer_sk where std.std_total_discount > ad.avg_discount order by c_customer_id limit 50;Explanation:
-
Common Table Expressions: Both the original and rewritten queries incorporate CTEs (
sales_total_discount,min_max_sales) to facilitate interim calculations and enhance readability. -
Fact Table: The
store_salestable is used as the primary data source, referenced in both queries. -
Joins: Both the original and rewritten queries incorporate the necessary joins per the join graph:
- Original: Implicit join in the
whereclause inside thesales_total_discount. - Rewritten: Utilizes explicit
JOINsyntax for better readability and optimizer performance.
- Original: Implicit join in the
-
Aggregate Functions: Both variants use
SUM,AVG, andMINin their logical computation processes. -
WHERE Clause: The original query uses a
HAVINGclause with a subquery to implement the comparison usingavg, while the rewritten one computes it in a separate CTE (avg_discount) for modular processing.
The rewritten query follows a transformation pattern that separates calculation and comparison, similar to your example, enhancing performance by avoiding redundant calculations.
-