Why aggregation is needed in SQL - Performance Analysis

Time Complexity: Why aggregation is needed

O(n)

Understanding Time Complexity

We want to understand how the time to run aggregation queries changes as data grows.

How does grouping and summarizing data affect the work the database does?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

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

This query counts how many employees are in each department by grouping rows.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Scanning each row in the employees table once.
• How many times: Once per row, to assign it to a group and update the count.

How Execution Grows With Input

As the number of employees grows, the database must look at each employee once.

Input Size (n)	Approx. Operations
10	10 operations (one per employee)
100	100 operations
1000	1000 operations

Pattern observation: The work grows directly with the number of rows.

Final Time Complexity

Time Complexity: O(n)

This means the time to run the aggregation grows in a straight line with the number of rows.

Common Mistake

[X] Wrong: "Aggregation queries are always slow because they do extra work."

[OK] Correct: Aggregation just looks at each row once, so it grows linearly, not slower or faster than scanning the data.

Interview Connect

Understanding how aggregation scales helps you explain query performance clearly and confidently.

Self-Check

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

Practice

1. Why do we use aggregation functions like SUM() or COUNT() in SQL?

easy

A. To summarize multiple rows into a single value

B. To delete rows from a table

C. To change the data type of a column

D. To create a new table

Solution

1. Step 1: Understand aggregation functions

   Aggregation functions like SUM and COUNT combine many rows into one summary value.

2. Step 2: Identify the purpose of aggregation

   They help get totals, counts, or averages instead of listing every row.

3. Final Answer:

   To summarize multiple rows into a single value -> Option A

4. Quick Check:

   Aggregation = summarize rows [OK]

Hint: Aggregation combines rows into one summary value [OK]

Common Mistakes:

• Thinking aggregation deletes data
• Confusing aggregation with data type changes
• Assuming aggregation creates new tables

2. Which of the following is the correct syntax to get the total sales from a table named Orders with a column Amount?

easy

A. SELECT COUNT(Amount) FROM Orders;

B. SELECT TOTAL(Amount) FROM Orders;

C. SELECT SUM(Amount) FROM Orders;

D. SELECT ADD(Amount) FROM Orders;

Solution

1. Step 1: Identify the correct aggregation function for total

   The function to add values is SUM(), so SUM(Amount) is correct.

2. Step 2: Check syntax correctness

   SUM(Amount) with SELECT and FROM table is valid SQL syntax.

3. Final Answer:

   SELECT SUM(Amount) FROM Orders; -> Option C

4. Quick Check:

   SUM() sums values [OK]

Hint: Use SUM() to add values in SQL [OK]

Common Mistakes:

• Using TOTAL() which is not standard SQL
• Using COUNT() instead of SUM() for totals
• Using ADD() which is not a SQL function

3. Given the table Sales with columns Region and Amount, what will this query return?

SELECT Region, COUNT(*) FROM Sales GROUP BY Region;

medium

A. The number of sales records per region

B. The total sales amount per region

C. The average sales amount per region

D. All sales records without grouping

Solution

1. Step 1: Understand COUNT(*) with GROUP BY

   COUNT(*) counts rows in each group defined by Region.

2. Step 2: Interpret the query result

   The query returns how many sales records exist for each Region.

3. Final Answer:

   The number of sales records per region -> Option A

4. Quick Check:

   COUNT(*) with GROUP BY = count rows per group [OK]

Hint: COUNT(*) counts rows per group [OK]

Common Mistakes:

• Thinking COUNT(*) sums amounts
• Confusing COUNT(*) with AVG()
• Ignoring GROUP BY effect

4. What is wrong with this SQL query if we want to find the average salary per department?

SELECT Department, AVG(Salary) FROM Employees;

medium

A. AVG() cannot be used on Salary

B. Missing GROUP BY clause for Department

C. SELECT must include only one column

D. Salary column name is incorrect

Solution

1. Step 1: Check aggregation with multiple columns

   When selecting Department and AVG(Salary), Department must be grouped.

2. Step 2: Identify missing GROUP BY

   The query lacks GROUP BY Department, causing error or wrong results.

3. Final Answer:

   Missing GROUP BY clause for Department -> Option B

4. Quick Check:

   Aggregation with columns needs GROUP BY [OK]

Hint: Use GROUP BY when mixing columns with aggregation [OK]

Common Mistakes:

• Forgetting GROUP BY with aggregation
• Thinking AVG() can't be used on numbers
• Assuming SELECT can have unrelated columns

5. You want to find the department with the highest total sales from the Sales table with columns Department and Amount. Which query correctly achieves this?

hard

A. SELECT Department, SUM(Amount) FROM Sales;

B. SELECT Department, MAX(Amount) FROM Sales;

C. SELECT Department FROM Sales WHERE Amount = MAX(Amount);

D. SELECT Department, SUM(Amount) FROM Sales GROUP BY Department ORDER BY SUM(Amount) DESC LIMIT 1;

Solution

1. Step 1: Aggregate total sales per department

   SUM(Amount) with GROUP BY Department calculates total sales per department.

2. Step 2: Order and limit to get highest total

   ORDER BY SUM(Amount) DESC sorts totals from highest to lowest, LIMIT 1 picks top department.

3. Final Answer:

   SELECT Department, SUM(Amount) FROM Sales GROUP BY Department ORDER BY SUM(Amount) DESC LIMIT 1; -> Option D

4. Quick Check:

   Group, sum, order desc, limit 1 = top total [OK]

Hint: Use ORDER BY SUM() DESC LIMIT 1 for top total [OK]

Common Mistakes:

• Using MAX(Amount) instead of SUM(Amount)
• Not grouping by Department
• Trying to filter with WHERE and aggregation