How GROUP BY changes query execution in SQL - Visual Walkthrough

Concept Flow - How GROUP BY changes query execution

Start with full table data

↓

Scan all rows

↓

Group rows by specified column(s)

↓

Aggregate each group (e.g., COUNT, SUM)

↓

Return one row per group with aggregated values

↓

End

The query first reads all rows, groups them by the chosen column(s), then calculates aggregates for each group, and finally returns one result row per group.

Execution Sample

SQL

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

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

Execution Table

Step	Action	Input Rows	Groups Formed	Aggregated Result	Output Rows
1	Scan all rows from employees table	10 rows	None yet	None yet	None yet
2	Group rows by department	10 rows	3 groups: Sales, HR, IT	None yet	None yet
3	Count employees in each group	Grouped rows	3 groups	Sales: 4, HR: 3, IT: 3	None yet
4	Return one row per group with counts	Aggregated data	3 groups	Same as previous	3 rows
5	Query ends	N/A	N/A	N/A	3 rows

💡 All rows processed and grouped; output contains one row per group with aggregated counts.

Variable Tracker

Variable	Start	After Step 2	After Step 3	Final
Input Rows	10 rows from employees	10 rows	Grouped into 3 groups	Grouped into 3 groups
Groups	None	3 groups formed	3 groups with counts	3 groups with counts
Aggregated Result	None	None	Counts calculated	Counts calculated
Output Rows	None	None	None	3 rows returned

Key Moments - 3 Insights

Why does the number of output rows decrease after GROUP BY?

Because rows are grouped by the specified column(s), multiple input rows combine into one group, so the output has one row per group instead of one per input row (see execution_table step 4).

Does GROUP BY change the original data in the table?

No, GROUP BY only organizes rows during query execution; it does not modify the original table data (see execution_table step 1 vs step 2).

What happens if you use GROUP BY without an aggregate function?

The query will return one row per group but without meaningful aggregation, often causing errors or unexpected results depending on SQL rules (not shown in this trace).

Visual Quiz - 3 Questions

Look at the execution_table, at which step are the rows grouped by department?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Check the 'Groups Formed' column in execution_table rows.

According to variable_tracker, how many groups exist after Step 3?

A None

B 1 group

C 3 groups

D 10 groups

💡 Hint

Look at the 'Groups' row after Step 3 in variable_tracker.

If the employees table had 5 departments instead of 3, how would the output rows change?

A Output rows would be 5

B Output rows would stay 3

C Output rows would be 10

D Output rows would be 1

💡 Hint

Refer to execution_table step 4 where output rows equal number of groups.

Concept Snapshot

GROUP BY groups rows by one or more columns.
Aggregates like COUNT or SUM calculate values per group.
Output returns one row per group.
Original table data is not changed.
Without aggregates, GROUP BY may cause errors or unexpected results.

Full Transcript

This visual execution trace shows how the SQL GROUP BY clause changes query execution. First, the query scans all rows from the employees table. Then, it groups these rows by the department column, forming three groups. Next, it calculates the count of employees in each group. Finally, the query returns one row per group with the aggregated counts. The number of output rows is less than the input rows because multiple rows combine into groups. GROUP BY organizes data during query execution but does not modify the original table. This trace helps beginners see step-by-step how grouping and aggregation work together in SQL.