LEAD in Databricks SQL

This page is a quick reference checkpoint for LEAD in Databricks SQL: behavior, syntax rules, edge cases, and a minimal example; plus the official vendor documentation.


Function Details

LEAD returns a value from the next row in the window partition.

Offset defaults to 1 when not specified; NULL is returned when offset goes beyond partition unless DEFAULT is provided

If this behavior feels unintuitive, the tutorial below explains the underlying pattern step-by-step.

LEAD(expr [, offset [, default ]]) OVER ( [PARTITION BY ...] ORDER BY ... )

SELECT LEAD(salary, 1, 0) OVER (PARTITION BY department ORDER BY hire_date) AS next_salary FROM employees

What should you do next?

If you came here to confirm syntax, you’re done. If you came here to get better at window functions, choose your next step.

Understand the pattern

LEAD is part of a bigger window-function pattern. If you want the “why”, start here: Lead Lag

Prove it with a real query

Reading docs is useful. Writing the query correctly under pressure is the skill.

Two Orders Before, Two Orders After: The Price Prophecy

Support Status

  • Supported: yes
  • Minimum Version: Databricks SQL Warehouses use a continuously updated engine without user-visible versions, so no minimum version can be specified.

Official Documentation

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.