Why filtering is essential in SQL - Challenge Your Understanding

Challenge - 5 Problems

❓ query_result

intermediate

Filtering rows with WHERE clause

Given the table Employees with columns id, name, and department, what will be the output of this query?

SELECT name FROM Employees WHERE department = 'Sales';

SQL

SELECT name FROM Employees WHERE department = 'Sales';

A [{"name": "Alice"}, {"name": "Bob"}, {"name": "Charlie"}]

B [{"name": "Alice"}, {"name": "Bob"}]

C []

D SyntaxError

💡 Hint

Filtering with WHERE limits rows to those matching the condition.

The WHERE clause filters rows to only those where department is 'Sales'. Only Alice and Bob belong to Sales.

🧠 Conceptual

intermediate

Why filtering improves query performance

Why is filtering data using conditions important in database queries?

A It reduces the amount of data processed and returned, improving speed and resource use.

B It increases the number of rows returned to show more data.

C It automatically creates indexes on columns.

D It changes the structure of the database tables.

💡 Hint

Think about how less data means faster work.

Filtering limits data to only what is needed, so queries run faster and use fewer resources.

📝 Syntax

advanced

Identify the correct filtering syntax

Which of the following SQL queries correctly filters employees with salary greater than 50000?

A SELECT * FROM Employees HAVING salary > 50000;

B SELECT * FROM Employees FILTER salary > 50000;

C SELECT * FROM Employees WHERE salary > 50000;

D SELECT * FROM Employees WHERE salary >= 50000;

💡 Hint

The WHERE clause is used for filtering rows before grouping.

Option C uses correct WHERE syntax. A uses invalid FILTER keyword. C uses HAVING which is for groups. D has wrong operator => instead of >=.

❓ optimization

advanced

Effect of filtering on query optimization

Consider a large table Orders. Which filtering approach helps the database optimize query performance best?

A Filtering after retrieving all rows without WHERE clause.

B Filtering on non-indexed columns with broad conditions.

C Filtering using OR conditions on multiple columns without indexes.

D Filtering on indexed columns with selective conditions.

💡 Hint

Indexes help the database find rows faster when filtering.

Filtering on indexed columns with selective conditions allows the database to quickly locate relevant rows, improving performance.

🔧 Debug

expert

Why does this filtering query return no rows?

Given the query:

SELECT * FROM Products WHERE price < 0;

Why might this query return an empty result set?

A Because prices are never negative, so no rows match the condition.

B Because the WHERE clause syntax is incorrect.

C Because the Products table is empty.

D Because the price column is not numeric.

💡 Hint

Think about what values prices usually have.

Prices are typically zero or positive, so filtering for price < 0 returns no rows.

Practice

1. Why is filtering data using the WHERE clause important in SQL?

easy

A. It automatically sorts the data alphabetically.

B. It changes the structure of the database tables.

C. It creates new tables from existing ones.

D. It helps retrieve only the rows that meet specific conditions.

Solution

1. Step 1: Understand the purpose of filtering

   Filtering is used to select only the rows that match certain criteria from a table.

2. Step 2: Identify what WHERE does

   The WHERE clause sets conditions to limit the rows returned by a query.

3. Final Answer:

   It helps retrieve only the rows that meet specific conditions. -> Option D

4. Quick Check:

   Filtering = Select specific rows [OK]

Hint: Remember: WHERE filters rows to get only what you need [OK]

Common Mistakes:

• Thinking WHERE changes table structure
• Confusing filtering with sorting
• Believing WHERE creates new tables

2. Which of the following is the correct syntax to filter rows where the column age is greater than 30?

easy

A. SELECT * FROM table FILTER age > 30;

B. SELECT * FROM table HAVING age > 30;

C. SELECT * FROM table WHERE age > 30;

D. SELECT * FROM table WHERE age => 30;

Solution

1. Step 1: Recall correct filtering syntax

   The WHERE clause is used with a condition like age > 30 to filter rows.

2. Step 2: Check each option's syntax

   SELECT * FROM table WHERE age > 30; uses correct syntax. SELECT * FROM table FILTER age > 30; uses FILTER which is invalid in SQL. SELECT * FROM table HAVING age > 30; uses HAVING which is for groups, not rows. SELECT * FROM table WHERE age => 30; uses => which is invalid operator.

3. Final Answer:

   SELECT * FROM table WHERE age > 30; -> Option C

4. Quick Check:

   WHERE + condition = correct filter [OK]

Hint: Use WHERE with correct operators like >, =, < [OK]

Common Mistakes:

• Using FILTER instead of WHERE
• Using HAVING without GROUP BY
• Using wrong comparison operators like =>

3. Given the table Employees with columns id, name, and salary, what will this query return?

SELECT name FROM Employees WHERE salary >= 50000;

medium

A. All employee names with salary equal to 50000 only

B. All employee names with salary greater than or equal to 50000

C. All employee names with salary less than 50000

D. All employee names regardless of salary

Solution

1. Step 1: Understand the WHERE condition

   The condition salary >= 50000 selects employees with salary 50000 or more.

2. Step 2: Analyze the SELECT clause

   The query selects only the name column for those filtered employees.

3. Final Answer:

   All employee names with salary greater than or equal to 50000 -> Option B

4. Quick Check:

   salary >= 50000 filters employees [OK]

Hint: >= means greater than or equal to, so includes 50000 [OK]

Common Mistakes:

• Thinking >= means only equal
• Confusing less than with greater than
• Selecting all columns instead of just names

4. Identify the error in this SQL query:

SELECT * FROM Products WHERE price => 100;

medium

A. The comparison operator => is invalid in SQL.

B. The WHERE clause is missing.

C. The SELECT statement should specify columns.

D. The semicolon at the end is not allowed.

Solution

1. Step 1: Check the comparison operator

   The operator => is not valid in SQL; the correct operator is >=.

2. Step 2: Verify other parts of the query

   The WHERE clause is present, SELECT * is valid, and semicolon is allowed.

3. Final Answer:

   The comparison operator => is invalid in SQL. -> Option A

4. Quick Check:

   Use >=, not => for comparisons [OK]

Hint: Use >= for 'greater or equal', not => [OK]

Common Mistakes:

• Using => instead of >=
• Removing WHERE clause accidentally
• Thinking semicolon is an error

5. You have a table Orders with columns order_id, customer_id, and status. You want to find all orders that are either 'shipped' or 'delivered'. Which query correctly filters these orders?

hard

A. SELECT * FROM Orders WHERE status = 'shipped' OR status = 'delivered';

B. SELECT * FROM Orders WHERE status = 'shipped' AND 'delivered';

C. SELECT * FROM Orders WHERE status IN (shipped, delivered);

D. SELECT * FROM Orders WHERE status = 'shipped', 'delivered';

Solution

1. Step 1: Understand filtering for multiple values

   To filter rows where status is either 'shipped' or 'delivered', use OR or IN.

2. Step 2: Analyze each option

   SELECT * FROM Orders WHERE status = 'shipped' OR status = 'delivered'; uses OR correctly. SELECT * FROM Orders WHERE status = 'shipped' AND 'delivered'; uses AND incorrectly. SELECT * FROM Orders WHERE status IN (shipped, delivered); omits quotes around strings, invalid syntax. SELECT * FROM Orders WHERE status = 'shipped', 'delivered'; has invalid syntax.

3. Final Answer:

   SELECT * FROM Orders WHERE status = 'shipped' OR status = 'delivered'; -> Option A

4. Quick Check:

   Use OR to combine conditions for filtering [OK]

Hint: Use OR or IN to filter multiple values [OK]

Common Mistakes:

• Using AND instead of OR for multiple options
• Incorrect syntax with commas in WHERE
• Confusing IN syntax