Why query patterns matter in SQL - Challenge Your Understanding

Challenge - 5 Problems

❓ query_result

intermediate

Output of a JOIN with filtering

Given two tables, Employees and Departments, what is the output of the following query?

SELECT e.name, d.department_name FROM Employees e JOIN Departments d ON e.department_id = d.id WHERE d.location = 'New York';

Assume Employees:
1, Alice, 10
2, Bob, 20
3, Carol, 10
Departments:
10, Sales, New York
20, Marketing, Boston

SQL

SELECT e.name, d.department_name FROM Employees e JOIN Departments d ON e.department_id = d.id WHERE d.location = 'New York';

A [{"name": "Bob", "department_name": "Marketing"}]

B [{"name": "Alice", "department_name": "Sales"}, {"name": "Carol", "department_name": "Sales"}]

C [{"name": "Alice", "department_name": "Sales"}, {"name": "Bob", "department_name": "Marketing"}, {"name": "Carol", "department_name": "Sales"}]

D []

💡 Hint

Focus on the JOIN condition and the WHERE clause filtering by location.

The query joins Employees with Departments on department_id and filters departments located in New York. Only employees in Sales (id 10) are included, which are Alice and Carol.

📝 Syntax

intermediate

Identify the syntax error in the query

Which option contains a syntax error in the SQL query?

SELECT name, age FROM Users WHERE age > 20 ORDER BY;

SQL

SELECT name, age FROM Users WHERE age > 20 ORDER BY;

A SELECT name, age FROM Users WHERE age > 20 ORDER BY;

B SELECT name, age FROM Users WHERE age > 20 ORDER BY age DESC;

C SELECT name, age FROM Users WHERE age > 20 ORDER BY 1;

D SELECT name, age FROM Users WHERE age > 20 ORDER BY age;

💡 Hint

ORDER BY must specify a column or expression to sort by.

Option A ends ORDER BY without specifying any column, causing a syntax error.

❓ optimization

advanced

Choose the most efficient query pattern for counting

You want to count how many orders each customer has placed. Which query pattern is the most efficient?

A SELECT customer_id FROM Orders GROUP BY customer_id HAVING COUNT(*) > 0;

B SELECT DISTINCT customer_id, (SELECT COUNT(*) FROM Orders o2 WHERE o2.customer_id = o1.customer_id) FROM Orders o1;

C SELECT customer_id, COUNT(*) FROM Orders GROUP BY customer_id;

D SELECT customer_id, COUNT(order_id) FROM Orders WHERE order_id IS NOT NULL GROUP BY customer_id;

💡 Hint

Consider how many times the Orders table is scanned in each query.

Option C uses GROUP BY with COUNT(*) scanning the table once. Option C uses a correlated subquery causing multiple scans. Option C only filters groups but does not count. Option C is similar to A but unnecessarily filters order_id IS NOT NULL which is redundant if order_id is always present.

🔧 Debug

advanced

Why does this query return no rows?

Given tables Products and Sales, why does this query return no rows?

SELECT p.product_name FROM Products p LEFT JOIN Sales s ON p.id = s.product_id WHERE s.sale_date > '2023-01-01';

Assume some products have no sales.

SQL

SELECT p.product_name FROM Products p LEFT JOIN Sales s ON p.id = s.product_id WHERE s.sale_date > '2023-01-01';

A Because the WHERE clause filters out rows where s.sale_date is NULL, removing unmatched products.

B Because LEFT JOIN requires an ON condition that matches all rows, which is missing.

C Because Products table is empty.

D Because sale_date column does not exist in Sales table.

💡 Hint

Think about how WHERE affects rows with NULLs from LEFT JOIN.

The WHERE clause filters on s.sale_date > '2023-01-01'. For products without sales, s.sale_date is NULL, so the condition fails and those rows are excluded, negating the LEFT JOIN effect.

🧠 Conceptual

expert

Why do query patterns affect database performance?

Which explanation best describes why different SQL query patterns can lead to very different performance even if they return the same results?

A Because databases ignore query patterns and optimize all queries to the same plan automatically.

B Because all queries are executed the same way internally, so patterns do not affect performance.

C Because query patterns only affect the order of results, not the speed of execution.

D Because query patterns determine how the database engine uses indexes, joins, and scans, affecting speed and resource use.

💡 Hint

Think about how databases process queries and use indexes.

Different query patterns can cause the database to choose different execution plans, use or ignore indexes, perform joins differently, and scan more or fewer rows, impacting performance.

Practice

1. Why is it important to use consistent query patterns when writing SQL queries?

easy

A. They make queries easier to read and maintain over time.

B. They always make queries run faster regardless of data size.

C. They allow you to write queries without knowing the database structure.

D. They prevent any syntax errors automatically.

Solution

1. Step 1: Understand the role of query patterns

   Query patterns help organize SQL commands in a clear and consistent way.

2. Step 2: Identify the main benefit of consistency

   Consistent patterns make queries easier to read and maintain, especially for teams or future updates.

3. Final Answer:

   They make queries easier to read and maintain over time. -> Option A

4. Quick Check:

   Consistency improves readability and maintenance [OK]

Hint: Think about teamwork and future you reading the query [OK]

Common Mistakes:

• Assuming patterns always improve speed
• Believing patterns remove need to know database
• Thinking patterns fix syntax errors automatically

2. Which of the following is the correct SQL syntax to select all columns from a table named employees?

easy

A. SELECT ALL FROM employees;

B. SELECT * FROM employees;

C. GET * FROM employees;

D. SELECT employees ALL;

Solution

1. Step 1: Recall the standard SQL SELECT syntax

   The correct way to select all columns is using SELECT * FROM table_name;.

2. Step 2: Check each option for syntax correctness

   SELECT * FROM employees; matches the correct syntax. Options B, C, and D use invalid keywords or order.

3. Final Answer:

   SELECT * FROM employees; -> Option B

4. Quick Check:

   Standard SELECT syntax uses * for all columns [OK]

Hint: Remember: SELECT * FROM table_name; is standard [OK]

Common Mistakes:

• Using GET instead of SELECT
• Using ALL without SELECT
• Incorrect keyword order

3. Given the table orders with columns order_id, customer_id, and amount, what will this query return?

SELECT customer_id, SUM(amount) FROM orders GROUP BY customer_id;

medium

A. A list of customers with the total amount they ordered.

B. All orders sorted by customer_id.

C. The average amount per order for each customer.

D. An error because SUM cannot be used without WHERE.

Solution

1. Step 1: Understand GROUP BY with aggregation

   The query groups rows by customer_id and sums the amount for each group.

2. Step 2: Interpret the SELECT clause

   It returns each customer_id with the total amount they ordered.

3. Final Answer:

   A list of customers with the total amount they ordered. -> Option A

4. Quick Check:

   GROUP BY + SUM gives totals per group [OK]

Hint: GROUP BY groups rows; SUM adds values per group [OK]

Common Mistakes:

• Confusing SUM with AVG
• Thinking GROUP BY sorts data
• Believing WHERE is needed for aggregation

4. Identify the error in this SQL query:

SELECT name, age FROM users WHERE age > 18 GROUP BY name;

medium

A. The query is correct as written.

B. WHERE clause cannot be used with GROUP BY.

C. SELECT must include only columns in GROUP BY.

D. GROUP BY should include all selected columns or use aggregation.

Solution

1. Step 1: Review SELECT and GROUP BY rules

   When using GROUP BY, all selected columns must be grouped or aggregated.

2. Step 2: Check the query columns

   The query selects name and age but only groups by name, so age is neither grouped nor aggregated.

3. Final Answer:

   GROUP BY should include all selected columns or use aggregation. -> Option D

4. Quick Check:

   All selected columns must be in GROUP BY or aggregated [OK]

Hint: All selected columns must be grouped or aggregated [OK]

Common Mistakes:

• Thinking WHERE conflicts with GROUP BY
• Ignoring missing aggregation for non-grouped columns
• Assuming query is correct without aggregation

5. You want to find customers who placed more than 3 orders and spent over $500 total. Which query pattern correctly achieves this?

SELECT customer_id, COUNT(*), SUM(amount) FROM orders GROUP BY customer_id HAVING COUNT(*) > 3 AND SUM(amount) > 500;

hard

A. Use WHERE to filter counts and sums after grouping.

B. Use GROUP BY only without HAVING or WHERE.

C. Use HAVING to filter groups based on aggregated values.

D. Use ORDER BY to filter groups with conditions.

Solution

1. Step 1: Understand filtering after aggregation

   WHERE filters rows before grouping; HAVING filters groups after aggregation.

2. Step 2: Identify correct clause for aggregated conditions

   Conditions on COUNT and SUM require HAVING, not WHERE.

3. Final Answer:

   Use HAVING to filter groups based on aggregated values. -> Option C

4. Quick Check:

   HAVING filters aggregated group results [OK]

Hint: Use HAVING for conditions on grouped data [OK]

Common Mistakes:

• Using WHERE instead of HAVING for aggregates
• Forgetting to group before filtering aggregates
• Using ORDER BY to filter data