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 sales_avg, hr_count FROM (SELECT AVG(salary) AS sales_avg FROM employees WHERE department = 'Sales' AND experience_years BETWEEN 1 AND 5 AND salary BETWEEN 50000 AND 60000) AS sales, (SELECT COUNT(*) AS hr_count FROM employees WHERE department = 'HR' AND experience_years BETWEEN 5 AND 10 AND salary BETWEEN 80000 AND 90000) AS hr FROM dummy WHERE d_dummy_sk = 1;[REWRITTEN QUERY]
SELECT AVG(CASE WHEN department = 'Sales' THEN salary END), COUNT(CASE WHEN department = 'HR' THEN salary END) FROM employees WHERE (department = 'Sales' AND experience_years BETWEEN 1 AND 5 AND salary BETWEEN 50000 AND 60000) OR (department = 'HR' AND experience_years BETWEEN 5 AND 10 AND salary BETWEEN 80000 AND 90000);[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_sales', 'web_sales']. Below is the join graph for these fact tables: ['store_sales(ss_customer_sk) references customer(c_customer_sk);', 'store_sales(ss_hdemo_sk) references household_demographics(hd_demo_sk);', 'store_sales(ss_item_sk) references item(i_item_sk);'] ['web_sales(ws_promo_sk) references promotion(p_promo_sk);', 'web_sales(ws_ship_addr_sk) references customer_address(ca_address_sk);', 'web_sales(ws_ship_customer_sk) references customer(c_customer_sk);']
- The original query must employ 2 joins.
- The original query must employ the following aggregate functions: ['count', 'avg'].
- The original query must employ the following operators in its WHERE clause: ['count', 'min', '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 are the new original and rewritten queries that adhere to the provided rewrite rule, using the TPC-DS schema:
Original Query:
SELECT store_count, web_avg FROM ( SELECT COUNT(*) AS store_count FROM store_sales JOIN customer ON store_sales.ss_customer_sk = customer.c_customer_sk WHERE customer.c_birth_year < 1990 AND store_sales.ss_quantity > 5 ) AS store_sales_count, ( SELECT AVG(ws_quantity) AS web_avg FROM web_sales JOIN customer ON web_sales.ws_ship_customer_sk = customer.c_customer_sk WHERE customer.c_birth_year >= 1990 AND web_sales.ws_quantity > 3 ) AS web_sales_avg FROM dummy WHERE d_dummy_sk = 1;Rewritten Query:
SELECT COUNT(CASE WHEN ss_quantity > 5 AND c_birth_year < 1990 THEN 1 END) AS store_count, AVG(CASE WHEN ws_quantity > 3 AND c_birth_year >= 1990 THEN ws_quantity END) AS web_avg FROM store_sales JOIN customer ON store_sales.ss_customer_sk = customer.c_customer_sk FULL OUTER JOIN web_sales ON web_sales.ws_ship_customer_sk = customer.c_customer_sk WHERE (ss_quantity > 5 AND c_birth_year < 1990) OR (ws_quantity > 3 AND c_birth_year >= 1990);Explanation: The rewritten query scans the necessary tables only once and uses CASE statements to conditionally calculate the count and average based on the requirements for each aggregate. The WHERE clause filters have been combined efficiently to maintain the equivalence to the original query. The use of a FULL OUTER JOIN ensures that both store_sales and web_sales data can be considered simultaneously in the context of customer attributes.