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 ss_items as (select i_item_id item_id ,sum(ss_ext_sales_price) ss_item_rev from store_sales ,item ,date_dim where ss_item_sk = i_item_sk and d_date in (select d_date from date_dim where d_week_seq = (select d_week_seq from date_dim where d_date = '2001-06-16')) and ss_sold_date_sk = d_date_sk group by i_item_id), cs_items as (select i_item_id item_id ,sum(cs_ext_sales_price) cs_item_rev from catalog_sales ,item ,date_dim where cs_item_sk = i_item_sk and d_date in (select d_date from date_dim where d_week_seq = (select d_week_seq from date_dim where d_date = '2001-06-16')) and cs_sold_date_sk = d_date_sk group by i_item_id), ws_items as (select i_item_id item_id ,sum(ws_ext_sales_price) ws_item_rev from web_sales ,item ,date_dim where ws_item_sk = i_item_sk and d_date in (select d_date from date_dim where d_week_seq =(select d_week_seq from date_dim where d_date = '2001-06-16')) and ws_sold_date_sk = d_date_sk group by i_item_id) select ss_items.item_id ,ss_item_rev ,ss_item_rev/((ss_item_rev+cs_item_rev+ws_item_rev)/3) * 100 ss_dev ,cs_item_rev ,cs_item_rev/((ss_item_rev+cs_item_rev+ws_item_rev)/3) * 100 cs_dev ,ws_item_rev ,ws_item_rev/((ss_item_rev+cs_item_rev+ws_item_rev)/3) * 100 ws_dev ,(ss_item_rev+cs_item_rev+ws_item_rev)/3 average from ss_items,cs_items,ws_items where ss_items.item_id=cs_items.item_id and ss_items.item_id=ws_items.item_id and ss_item_rev between 0.9 * cs_item_rev and 1.1 * cs_item_rev and ss_item_rev between 0.9 * ws_item_rev and 1.1 * ws_item_rev and cs_item_rev between 0.9 * ss_item_rev and 1.1 * ss_item_rev and cs_item_rev between 0.9 * ws_item_rev and 1.1 * ws_item_rev and ws_item_rev between 0.9 * ss_item_rev and 1.1 * ss_item_rev and ws_item_rev between 0.9 * cs_item_rev and 1.1 * cs_item_rev order by item_id ,ss_item_rev limit 100;[REWRITTEN QUERY]
with dates as (select d_date from date_dim where d_week_seq = (select d_week_seq from date_dim where d_date = '2001-06-16')), ss_items as (select i_item_id item_id ,sum(ss_ext_sales_price) ss_item_rev from store_sales ,item ,date_dim where ss_item_sk = i_item_sk and d_date in (select d_date from dates) and ss_sold_date_sk = d_date_sk group by i_item_id), cs_items as (select i_item_id item_id ,sum(cs_ext_sales_price) cs_item_rev from catalog_sales ,item ,date_dim where cs_item_sk = i_item_sk and d_date in (select d_date from dates) and cs_sold_date_sk = d_date_sk group by i_item_id), ws_items as (select i_item_id item_id ,sum(ws_ext_sales_price) ws_item_rev from web_sales ,item ,date_dim where ws_item_sk = i_item_sk and d_date in (select d_date from dates) and ws_sold_date_sk = d_date_sk group by i_item_id) select ss_items.item_id ,ss_item_rev ,ss_item_rev/((ss_item_rev+cs_item_rev+ws_item_rev)/3) * 100 ss_dev ,cs_item_rev ,cs_item_rev/((ss_item_rev+cs_item_rev+ws_item_rev)/3) * 100 cs_dev ,ws_item_rev ,ws_item_rev/((ss_item_rev+cs_item_rev+ws_item_rev)/3) * 100 ws_dev ,(ss_item_rev+cs_item_rev+ws_item_rev)/3 average from ss_items,cs_items,ws_items where ss_items.item_id=cs_items.item_id and ss_items.item_id=ws_items.item_id and ss_item_rev between 0.9 * cs_item_rev and 1.1 * cs_item_rev and ss_item_rev between 0.9 * ws_item_rev and 1.1 * ws_item_rev and cs_item_rev between 0.9 * ss_item_rev and 1.1 * ss_item_rev and cs_item_rev between 0.9 * ws_item_rev and 1.1 * ws_item_rev and ws_item_rev between 0.9 * ss_item_rev and 1.1 * ss_item_rev and ws_item_rev between 0.9 * cs_item_rev and 1.1 * cs_item_rev order by item_id ,ss_item_rev 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: ['web_sales', 'catalog_returns']. Below is the join graph for these fact tables: ['web_sales(ws_ship_mode_sk) references ship_mode(sm_ship_mode_sk);', 'web_sales(ws_bill_customer_sk) references customer(c_customer_sk);', 'web_sales(ws_promo_sk) references promotion(p_promo_sk);'] ['catalog_returns(cr_ship_date_sk) references date_dim(d_date_sk);', 'catalog_returns(cr_ship_mode_sk) references ship_mode(sm_ship_mode_sk);', 'catalog_returns(cr_returned_time_sk) references time_dim(t_time_sk);']
- The original query must employ 4 joins.
- The original query must employ the following operators in its WHERE clause: ['sum', 'avg', 'max'].
- 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
Here's a pair of original and rewritten SQL queries leveraging Common Table Expressions (CTEs) and the specified fact tables and operations. The transformation uses the same principle of refactoring common subqueries into a separate CTE.
[ORIGINAL QUERY]
with sales_data as ( select ws_ship_mode_sk, sum(ws_ext_sales_price) as total_sales, avg(ws_ext_sales_price) as avg_sales from web_sales join ship_mode on ws_ship_mode_sk = sm_ship_mode_sk join customer on ws_bill_customer_sk = c_customer_sk where ws_promo_sk is not null group by ws_ship_mode_sk ), returns_data as ( select cr_ship_date_sk, max(cr_return_amt) as max_return_amt from catalog_returns join ship_mode on cr_ship_mode_sk = sm_ship_mode_sk join date_dim on cr_ship_date_sk = d_date_sk where cr_returned_time_sk is not null group by cr_ship_date_sk ) select ship_mode.sm_type, sales_data.total_sales, sales_data.avg_sales, returns_data.max_return_amt from sales_data join returns_data on sales_data.ws_ship_mode_sk = returns_data.cr_ship_date_sk join ship_mode on sales_data.ws_ship_mode_sk = ship_mode.sm_ship_mode_sk order by ship_mode.sm_type, sales_data.total_sales limit 100;[REWRITTEN QUERY]
with promo_ship_modes as ( select distinct ws_promo_sk, ws_ship_mode_sk from web_sales where ws_promo_sk is not null ), sales_data as ( select ws_ship_mode_sk, sum(ws_ext_sales_price) as total_sales, avg(ws_ext_sales_price) as avg_sales from web_sales join promo_ship_modes on web_sales.ws_ship_mode_sk = promo_ship_modes.ws_ship_mode_sk join customer on ws_bill_customer_sk = c_customer_sk group by ws_ship_mode_sk ), returns_data as ( select cr_ship_date_sk, max(cr_return_amt) as max_return_amt from catalog_returns join ship_mode on cr_ship_mode_sk = sm_ship_mode_sk join date_dim on cr_ship_date_sk = d_date_sk where cr_returned_time_sk is not null group by cr_ship_date_sk ) select ship_mode.sm_type, sales_data.total_sales, sales_data.avg_sales, returns_data.max_return_amt from sales_data join returns_data on sales_data.ws_ship_mode_sk = returns_data.cr_ship_date_sk join ship_mode on sales_data.ws_ship_mode_sk = ship_mode.sm_ship_mode_sk order by ship_mode.sm_type, sales_data.total_sales limit 100;Explanation
- CTE Optimization: In the rewritten query, the logic that identifies shipment modes with promotions (
promo_ship_modes) is extracted into a separate CTE. This eliminates the need to apply thews_promo_sk is not nullfilter multiple times across the join operations. - Equivalent Logic: The rewritten query maintains the logic of the original but uses the additional CTE for potentially improved performance due to reduced redundancy.
- Structure: The structure of joins remains compliant with the schema restrictions and specified operations (
sum,avg,max) are retained as part of the aggregations.
- CTE Optimization: In the rewritten query, the logic that identifies shipment modes with promotions (