OVER clause with ORDER BY in SQL - Step-by-Step Execution

Concept Flow - OVER clause with ORDER BY

Start Query

↓

Identify Window Function

↓

Parse OVER Clause

↓

Apply ORDER BY inside OVER

↓

Calculate Function per Ordered Rows

↓

Return Result Set with Window Function Values

↓

End Query

The query starts by identifying the window function, then parses the OVER clause including ORDER BY, applies the ordering to rows, calculates the function per ordered rows, and returns the result.

Execution Sample

SQL

SELECT name, salary,
       RANK() OVER (ORDER BY salary DESC) AS salary_rank
FROM employees;

This query ranks employees by salary in descending order using the OVER clause with ORDER BY.

Execution Table

Step	Action	Rows Ordered	Function Calculation	Output Row
1	Start query execution	N/A	N/A	N/A
2	Order rows by salary DESC	Alice(9000), Bob(8000), Carol(8000), Dave(7000)	N/A	N/A
3	Calculate RANK() for Alice	Same as above	Rank=1	Alice, 9000, 1
4	Calculate RANK() for Bob	Same as above	Rank=2	Bob, 8000, 2
5	Calculate RANK() for Carol	Same as above	Rank=2 (tie)	Carol, 8000, 2
6	Calculate RANK() for Dave	Same as above	Rank=4	Dave, 7000, 4
7	Return all rows with ranks	Same as above	Completed	All rows with ranks
8	End query	N/A	N/A	N/A

💡 All rows processed and ranked according to salary descending order.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 5	After Step 6	Final
Ordered Rows	N/A	Alice(9000), Bob(8000), Carol(8000), Dave(7000)	Same	Same	Same	Same	Same
Current Row	N/A	N/A	Alice	Bob	Carol	Dave	N/A
Rank	N/A	N/A	1	2	2	4	N/A

Key Moments - 2 Insights

Why do Bob and Carol have the same rank 2 instead of different ranks?

Because the ORDER BY inside OVER orders by salary descending, and Bob and Carol have the same salary (8000), so RANK() assigns the same rank to tied values as shown in execution_table rows 4 and 5.

What happens if we remove ORDER BY inside the OVER clause?

Without ORDER BY, the window function like RANK() cannot assign ranks based on order, so it may treat all rows as equal or produce unexpected results. The execution_table step 2 ordering would be missing.

Visual Quiz - 3 Questions

Look at the execution_table at step 4, what is the rank assigned to Bob?

A 2

B 1

C 3

D 4

💡 Hint

Check the 'Function Calculation' column at step 4 in execution_table.

At which step does the query order the rows by salary descending?

A Step 1

B Step 2

C Step 3

D Step 7

💡 Hint

Look at the 'Action' column describing ordering in execution_table.

If Carol's salary changed to 8500, what would be her new rank?

A 2

B 3

C 1

D 4

💡 Hint

Refer to variable_tracker and how ranks are assigned based on salary order.

Concept Snapshot

OVER clause with ORDER BY lets you apply window functions like RANK() over ordered rows.
Syntax: FUNCTION() OVER (ORDER BY column [ASC|DESC])
Rows are sorted inside the window before function calculation.
Ties get same rank with RANK().
Useful for ranking, running totals, and more.

Full Transcript

This visual execution trace shows how the SQL OVER clause with ORDER BY works. The query orders rows by salary descending, then calculates the RANK() function per row in that order. Ties in salary get the same rank. The execution table walks through each step, showing ordering and rank assignment. The variable tracker shows how the ordered rows and ranks change step by step. Key moments clarify why tied salaries share ranks and what happens without ORDER BY. The quiz tests understanding of ranks at specific steps and effects of data changes.

Practice

1. What does the OVER clause with ORDER BY do in SQL?

easy

A. It creates a new table sorted by the specified column.

B. It performs calculations on rows in a specific order without grouping them.

C. It filters rows based on order conditions.

D. It groups rows and then orders the groups.

Solution

1. Step 1: Understand the OVER clause

   The OVER clause allows window functions to work on a set of rows related to the current row without grouping them.

2. Step 2: Role of ORDER BY inside OVER

   ORDER BY inside OVER defines the order in which rows are processed for functions like ROW_NUMBER() or SUM() running totals.

3. Final Answer:

   It performs calculations on rows in a specific order without grouping them. -> Option B

4. Quick Check:

   OVER with ORDER BY = ordered calculations without grouping [OK]

Hint: OVER with ORDER BY orders rows for calculations, no grouping needed [OK]

Common Mistakes:

• Thinking OVER groups rows like GROUP BY
• Confusing ORDER BY inside OVER with filtering
• Assuming it creates a new sorted table

2. Which of the following is the correct syntax to assign row numbers ordered by salary using the OVER clause?

easy

A. SELECT ROW_NUMBER(ORDER BY salary) AS rank FROM employees;

B. SELECT ROW_NUMBER() AS rank OVER ORDER BY salary FROM employees;

C. SELECT ROW_NUMBER() ORDER BY salary FROM employees;

D. SELECT ROW_NUMBER() OVER (ORDER BY salary) AS rank FROM employees;

Solution

1. Step 1: Identify correct ROW_NUMBER() syntax

   ROW_NUMBER() requires OVER() with ORDER BY inside parentheses to define ordering.

2. Step 2: Check each option

   SELECT ROW_NUMBER() OVER (ORDER BY salary) AS rank FROM employees; correctly uses ROW_NUMBER() OVER (ORDER BY salary). Others miss parentheses or misplace clauses.

3. Final Answer:

   SELECT ROW_NUMBER() OVER (ORDER BY salary) AS rank FROM employees; -> Option D

4. Quick Check:

   ROW_NUMBER() needs OVER(ORDER BY ...) [OK]

Hint: ROW_NUMBER() must be followed by OVER(ORDER BY column) [OK]

Common Mistakes:

• Omitting OVER() parentheses
• Placing ORDER BY outside OVER()
• Using ROW_NUMBER() without OVER

3. Given the table sales with columns id, amount, what is the output of this query?

SELECT id, amount, SUM(amount) OVER (ORDER BY id) AS running_total FROM sales ORDER BY id;

medium

A. The query returns an error due to missing GROUP BY.

B. Each row shows id, amount, and total sum of all amounts repeated.

C. Each row shows id, amount, and a running total of amounts ordered by id.

D. Rows are grouped by id with sum of amounts per group.

Solution

1. Step 1: Understand SUM() OVER (ORDER BY id)

   This calculates a running total of amount, adding amounts in order of id for each row.

2. Step 2: Analyze output per row

   Each row shows its id, amount, and the sum of amounts from first id up to current id.

3. Final Answer:

   Each row shows id, amount, and a running total of amounts ordered by id. -> Option C

4. Quick Check:

   SUM() OVER with ORDER BY = running total [OK]

Hint: SUM() OVER(ORDER BY) gives running totals, not grouped sums [OK]

Common Mistakes:

• Thinking it sums all rows for each row
• Expecting GROUP BY to be required
• Confusing running total with grouped sum

4. Identify the error in this query:

SELECT id, RANK() OVER ORDER BY score FROM players;

medium

A. Missing parentheses after OVER and ORDER BY inside them.

B. RANK() cannot be used with OVER clause.

C. ORDER BY should be outside the OVER clause.

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

Solution

1. Step 1: Check syntax of RANK() with OVER

   RANK() requires OVER() with parentheses enclosing ORDER BY clause.

2. Step 2: Identify missing parentheses

   The query misses parentheses after OVER and does not put ORDER BY inside them, causing syntax error.

3. Final Answer:

   Missing parentheses after OVER and ORDER BY inside them. -> Option A

4. Quick Check:

   OVER() must have parentheses with ORDER BY inside [OK]

Hint: Always use OVER(...) with parentheses enclosing ORDER BY [OK]

Common Mistakes:

• Writing OVER without parentheses
• Placing ORDER BY outside OVER()
• Assuming RANK() works without OVER

5. You want to assign a rank to employees based on their salary, but if two employees have the same salary, they should get the same rank and the next rank should skip accordingly. Which query correctly uses the OVER clause with ORDER BY to achieve this?

hard

A. SELECT employee_id, salary, RANK() OVER (ORDER BY salary DESC) AS salary_rank FROM employees;

B. SELECT employee_id, salary, ROW_NUMBER() OVER (ORDER BY salary DESC) AS salary_rank FROM employees;

C. SELECT employee_id, salary, DENSE_RANK() OVER (ORDER BY salary DESC) AS salary_rank FROM employees;

D. SELECT employee_id, salary, RANK() OVER ORDER BY salary DESC AS salary_rank FROM employees;

Solution

1. Step 1: Understand ranking functions

   RANK() assigns same rank to ties and skips ranks after ties; DENSE_RANK() assigns same rank but no skips; ROW_NUMBER() assigns unique numbers.

2. Step 2: Check syntax and behavior

   SELECT employee_id, salary, RANK() OVER (ORDER BY salary DESC) AS salary_rank FROM employees; uses RANK() with correct OVER(ORDER BY salary DESC) syntax, matching requirement. SELECT employee_id, salary, RANK() OVER ORDER BY salary DESC AS salary_rank FROM employees; has syntax error. ROW_NUMBER() and DENSE_RANK() do not skip ranks after ties.

3. Final Answer:

   SELECT employee_id, salary, RANK() OVER (ORDER BY salary DESC) AS salary_rank FROM employees; -> Option A

4. Quick Check:

   RANK() with OVER(ORDER BY) skips ranks after ties [OK]

Hint: Use RANK() OVER(ORDER BY) for ranks with gaps on ties [OK]

Common Mistakes:

• Using ROW_NUMBER() which never skips ranks
• Using DENSE_RANK() which does not skip ranks
• Missing parentheses in OVER clause