GROUP BY single column in SQL - Step-by-Step Execution

Concept Flow - GROUP BY single column

Start with table data

↓

Select column to group by

↓

Scan all rows

↓

Group rows by unique values in that column

↓

Apply aggregate functions (if any) per group

↓

Return grouped result set

The query groups rows by unique values in one column, then aggregates data per group.

Execution Sample

SQL

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

This query counts employees in each department by grouping rows by department.

Execution Table

Step	Action	Current Row	Group Key	Groups Formed	Aggregate Count per Group
1	Read row	('Sales', 'Alice')	Sales	{Sales}	{Sales:1}
2	Read row	('HR', 'Bob')	HR	{Sales, HR}	{Sales:1, HR:1}
3	Read row	('Sales', 'Charlie')	Sales	{Sales, HR}	{Sales:2, HR:1}
4	Read row	('IT', 'David')	IT	{Sales, HR, IT}	{Sales:2, HR:1, IT:1}
5	Read row	('HR', 'Eve')	HR	{Sales, HR, IT}	{Sales:2, HR:2, IT:1}
6	End of rows	N/A	N/A	{Sales, HR, IT}	{Sales:2, HR:2, IT:1}

💡 All rows processed; groups formed by unique department values.

Variable Tracker

Variable	Start	After 1	After 2	After 3	After 4	After 5	Final
Groups	{}	{Sales}	{Sales, HR}	{Sales, HR}	{Sales, HR, IT}	{Sales, HR, IT}	{Sales, HR, IT}
Aggregate Count	{}	{Sales:1}	{Sales:1, HR:1}	{Sales:2, HR:1}	{Sales:2, HR:1, IT:1}	{Sales:2, HR:2, IT:1}	{Sales:2, HR:2, IT:1}

Key Moments - 2 Insights

Why does the group 'Sales' count increase on step 3 instead of creating a new group?

Because 'Sales' was already seen in step 1, the row is added to the existing 'Sales' group, increasing its count (see execution_table row 3).

What happens if a row has a department not seen before?

A new group is created for that department, as shown in step 4 with 'IT' (execution_table row 4).

Visual Quiz - 3 Questions

Look at the execution table, what is the aggregate count for 'HR' after step 5?

A 1

B 3

C 2

D 0

💡 Hint

Check the 'Aggregate Count per Group' column at step 5 in the execution_table.

At which step is the 'IT' group first created?

A Step 3

B Step 4

C Step 2

D Step 5

💡 Hint

Look at the 'Groups Formed' column to see when 'IT' appears.

If the query did not have GROUP BY, what would happen to the counts?

A Counts would be total for all rows combined

B Counts would be per department as usual

C Counts would be zero

D Query would fail

💡 Hint

Without GROUP BY, aggregate functions apply to all rows as one group.

Concept Snapshot

GROUP BY single column syntax:
SELECT column, aggregate_function()
FROM table
GROUP BY column;
Groups rows by unique values in one column.
Aggregates apply per group.
Useful to summarize data by categories.

Full Transcript

The GROUP BY single column concept groups rows from a table by unique values in one column. The query scans each row, identifies the group key from the chosen column, and collects rows into groups. Aggregate functions like COUNT calculate values per group. For example, counting employees per department groups rows by department and counts members in each group. The execution table shows each row processed, groups formed, and counts updated. Beginners often wonder why counts increase for existing groups instead of creating new ones; this happens because rows with the same group key belong to the same group. Another point is when a new group is created for a previously unseen value. Without GROUP BY, aggregate functions apply to the entire table as one group, not per category. This visual trace helps understand how GROUP BY organizes data step-by-step.

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 a specified column.

D. It filters rows based on a condition.

Solution

1. Step 1: Understand the purpose of GROUP BY

   The GROUP BY clause collects rows with the same value in the specified column into groups.

2. Step 2: Differentiate from other clauses

   Unlike ORDER BY which sorts, or WHERE which filters, GROUP BY organizes data for aggregation.

3. Final Answer:

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

4. Quick Check:

   GROUP BY = grouping rows by column [OK]

Hint: GROUP BY collects rows sharing column values [OK]

Common Mistakes:

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

2. Which of the following is the correct syntax to group data by the column department?

easy

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

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

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

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

Solution

1. Step 1: Identify correct GROUP BY usage

   The GROUP BY clause must follow FROM and group by the column named.

2. Step 2: Check each option's clause

   SELECT department, COUNT(*) FROM employees GROUP BY department; uses GROUP BY correctly; others use ORDER BY, WHERE, HAVING incorrectly here.

3. Final Answer:

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

4. Quick Check:

   GROUP BY syntax = SELECT ... GROUP BY column [OK]

Hint: GROUP BY follows FROM and groups by column [OK]

Common Mistakes:

• Using ORDER BY instead of GROUP BY
• Using WHERE to group data
• Using HAVING without aggregation

3. Given the table sales with columns region and amount, what is the output 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 total sales amount for each region.

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

D. A list of regions sorted by amount.

Solution

1. Step 1: Understand GROUP BY with SUM()

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

2. Step 2: Predict output format

   The output shows each region once with the total amount of sales in that region.

3. Final Answer:

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

4. Quick Check:

   GROUP BY + SUM() = grouped sums [OK]

Hint: GROUP BY + SUM() gives totals per group [OK]

Common Mistakes:

• Thinking SUM() can't be used with GROUP BY
• Expecting ungrouped list
• Confusing sorting with grouping

4. Identify the error in this SQL query:

SELECT department, COUNT(*) FROM employees;

medium

A. The query is correct and will run without errors.

B. COUNT(*) cannot be used without WHERE clause.

C. department cannot be selected without aggregation.

D. Missing GROUP BY clause for the department column.

Solution

1. Step 1: Check SELECT with aggregation

   COUNT(*) is an aggregate but department is not aggregated or grouped.

2. Step 2: Identify missing GROUP BY

   To select department with COUNT(*), GROUP BY department is required.

3. Final Answer:

   Missing GROUP BY clause for the department column. -> Option D

4. Quick Check:

   Non-aggregated columns need GROUP BY [OK]

Hint: Non-aggregated columns need GROUP BY [OK]

Common Mistakes:

• Ignoring missing GROUP BY
• Thinking COUNT(*) needs WHERE
• Assuming query runs without error

5. You have a table orders with columns customer_id, order_date, and total. You want to find the average order total per customer but only for customers who have placed more than 3 orders. Which query correctly achieves this?

hard

A. SELECT customer_id, AVG(total) FROM orders GROUP BY customer_id HAVING COUNT(*) > 3;

B. SELECT customer_id, AVG(total) FROM orders WHERE COUNT(*) > 3 GROUP BY customer_id;

C. SELECT customer_id, AVG(total) FROM orders GROUP BY customer_id WHERE COUNT(*) > 3;

D. SELECT customer_id, AVG(total) FROM orders HAVING COUNT(*) > 3 GROUP BY customer_id;

Solution

1. Step 1: Use GROUP BY to group orders by customer_id

   This groups all orders per customer to calculate aggregates.

2. Step 2: Use HAVING to filter groups with more than 3 orders

   HAVING filters groups after aggregation; WHERE cannot filter aggregates.

3. Final Answer:

   SELECT customer_id, AVG(total) FROM orders GROUP BY customer_id HAVING COUNT(*) > 3; -> Option A

4. Quick Check:

   HAVING filters groups, WHERE filters rows [OK]

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

Common Mistakes:

• Using WHERE to filter aggregated counts
• Placing HAVING before GROUP BY
• Not filtering groups at all