This page is a quick reference checkpoint for MAX OVER in Databricks SQL: behavior, syntax rules, edge cases, and a minimal example; plus the official vendor documentation.
MAX OVER returns the largest value in the window frame.
Supports window frames; example shows ORDER BY and RANGE BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW
If this behavior feels unintuitive, the tutorial below explains the underlying pattern step-by-step.
MAX(expr) OVER ( [PARTITION BY ...] [ORDER BY ...] [window_frame] )
SELECT department, salary, MAX(salary) OVER (PARTITION BY department) AS max_over_department FROM employees;
If you came here to confirm syntax, you’re done. If you came here to get better at window functions, choose your next step.
MAX OVER is part of a bigger window-function pattern. If you want the “why”, start here: Aggregate Window Functions
Reading docs is useful. Writing the query correctly under pressure is the skill.
For the authoritative spec, use the vendor docs. This page is the fast “sanity check”.
View Databricks SQL Documentation →Looking for more functions across all SQL dialects? Visit the full SQL Dialects & Window Functions Documentation.