GROUP BY with aggregate functions in SQL - Time & Space Complexity

Time Complexity: GROUP BY with aggregate functions

O(n)

Understanding Time Complexity

When using GROUP BY with aggregate functions, we want to know how the work grows as the data gets bigger.

How does the database handle grouping and summarizing many rows?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

SELECT department, COUNT(*) AS employee_count, AVG(salary) AS avg_salary
FROM employees
GROUP BY department;

This query groups employees by their department and calculates the number of employees and average salary per department.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Scanning all rows in the employees table once.
• How many times: Once for each row (n times, where n is total rows).

How Execution Grows With Input

As the number of rows grows, the database must look at each row to group and calculate aggregates.

Input Size (n)	Approx. Operations
10	About 10 row checks and group updates
100	About 100 row checks and group updates
1000	About 1000 row checks and group updates

Pattern observation: The work grows roughly in direct proportion to the number of rows.

Final Time Complexity

Time Complexity: O(n)

This means the time to run the query grows linearly with the number of rows in the table.

Common Mistake

[X] Wrong: "GROUP BY makes the query run slower by multiplying work for each group."

[OK] Correct: The database still scans each row once; grouping just organizes results, not repeating the scan.

Interview Connect

Understanding how grouping affects query time helps you explain data summarization clearly and shows you know how databases handle big data efficiently.

Self-Check

"What if we added an ORDER BY after GROUP BY? How would the time complexity change?"

Practice

1. What does the GROUP BY clause do in an SQL query?

easy

A. It deletes duplicate rows from the table.

B. It sorts the rows in ascending order.

C. It groups rows that have the same values in specified columns.

D. It filters rows based on a condition.

Solution

1. Step 1: Understand the purpose of GROUP BY

   The GROUP BY clause is used to group rows that share the same values in one or more columns.

2. Step 2: Differentiate from other clauses

   Sorting is done by ORDER BY, filtering by WHERE, and removing duplicates by DISTINCT, not GROUP BY.

3. Final Answer:

   It groups rows that have the same values in specified columns. -> Option C

4. Quick Check:

   GROUP BY = groups rows by column values [OK]

Hint: GROUP BY groups rows by column values, not sorting or filtering [OK]

Common Mistakes:

• Confusing GROUP BY with ORDER BY
• Thinking GROUP BY filters rows
• Assuming GROUP BY removes duplicates

2. Which of the following SQL queries correctly uses GROUP BY to count employees per department?

easy

A. SELECT department, COUNT(*) FROM employees GROUP BY.;

B. SELECT department, COUNT(*) FROM employees GROUP BY department.;

C. SELECT department, COUNT(*) FROM employees WHERE department GROUP BY.;

D. SELECT department, COUNT(*) FROM employees.;

Solution

1. Step 1: Check the syntax of GROUP BY usage

   The correct syntax requires specifying the column after GROUP BY and using aggregate functions properly.

2. Step 2: Analyze each option

   Only SELECT department, COUNT(*) FROM employees GROUP BY department; correctly groups by department and counts employees. The other options have syntax errors: missing column after GROUP BY, no GROUP BY clause, or invalid WHERE syntax.

3. Final Answer:

   SELECT department, COUNT(*) FROM employees GROUP BY department; -> Option B

4. Quick Check:

   GROUP BY column + aggregate function = correct syntax [OK]

Hint: GROUP BY must be followed by column names, aggregate functions used outside [OK]

Common Mistakes:

• Omitting column after GROUP BY
• Using WHERE incorrectly with GROUP BY
• Missing aggregate function with GROUP BY

3. Given the table sales with columns region and amount, what is the result of this query?

SELECT region, SUM(amount) FROM sales GROUP BY region;

medium

A. A list of all sales amounts without grouping.

B. A list of regions with the average sales amount.

C. An error because SUM() cannot be used with GROUP BY.

D. A list of regions with the total sales amount for each region.

Solution

1. Step 1: Understand the query components

   The query groups rows by region and calculates the sum of amount for each group.

2. Step 2: Determine the output

   The output will show each region once with the total sales amount summed up.

3. Final Answer:

   A list of regions with the total sales amount for each region. -> Option D

4. Quick Check:

   GROUP BY region + SUM(amount) = total per region [OK]

Hint: SUM with GROUP BY gives total per group, not average or error [OK]

Common Mistakes:

• Confusing SUM with AVG
• Expecting no grouping effect
• Thinking SUM causes error with GROUP BY

4. Identify the error in this SQL query:

SELECT department, AVG(salary) FROM employees WHERE department GROUP BY department;

medium

A. Missing condition after WHERE clause.

B. AVG() cannot be used with GROUP BY.

C. GROUP BY should come before WHERE.

D. department cannot be selected with AVG().

Solution

1. Step 1: Analyze the WHERE clause

   The WHERE clause requires a condition, but here it only has 'department' which is incomplete and invalid.

2. Step 2: Check GROUP BY and AVG usage

   GROUP BY after WHERE is correct, and AVG() can be used with GROUP BY, so no error there.

3. Final Answer:

   Missing condition after WHERE clause. -> Option A

4. Quick Check:

   WHERE needs a condition, not just a column name [OK]

Hint: WHERE must have a condition; column alone is invalid [OK]

Common Mistakes:

• Using WHERE without condition
• Thinking GROUP BY order is wrong
• Believing AVG() can't be grouped

5. You have a products table with columns category, price, and stock. Which query shows the average price and total stock for each category, but only for categories with more than 10 products?

hard

A. SELECT category, AVG(price), SUM(stock) FROM products GROUP BY category HAVING COUNT(*) > 10;

B. SELECT category, AVG(price), SUM(stock) FROM products WHERE COUNT(*) > 10 GROUP BY category;

C. SELECT category, AVG(price), SUM(stock) FROM products GROUP BY category WHERE COUNT(*) > 10;

D. SELECT category, AVG(price), SUM(stock) FROM products HAVING COUNT(*) > 10 GROUP BY category;

Solution

1. Step 1: Understand filtering groups with HAVING

   To filter groups based on aggregate conditions, use HAVING after GROUP BY.

2. Step 2: Analyze each option's clause order

   Only SELECT category, AVG(price), SUM(stock) FROM products GROUP BY category HAVING COUNT(*) > 10; correctly uses GROUP BY then HAVING. Using WHERE with COUNT(*) is invalid (WHERE processes rows before grouping), and placing HAVING before GROUP BY or incorrect clause ordering is invalid syntax.

3. Final Answer:

   SELECT category, AVG(price), SUM(stock) FROM products GROUP BY category HAVING COUNT(*) > 10; -> Option A

4. Quick Check:

   Use HAVING to filter groups after GROUP BY [OK]

Hint: Use HAVING after GROUP BY to filter groups by aggregate [OK]

Common Mistakes:

• Using WHERE to filter aggregate results
• Placing HAVING before GROUP BY
• Confusing clause order in SQL