LEAD in Snowflake

This page is a quick reference checkpoint for LEAD in Snowflake: 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.

Accesses data in a subsequent row in the same result set without needing a self-join; supports an offset (default 1), a default return if offset is out of bounds, and {IGNORE | RESPECT} NULLS semantics. Default offset is 1; default default value is NULL. The PARTITION BY clause partitions the result and ORDER BY defines ordering in each partition.

Warning: When IGNORE NULLS is specified, a maximum offset of 1,000,000 is enforced.

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

LEAD ( <expr> [ , <offset> , <default> ] ) [ { IGNORE | RESPECT } NULLS ] OVER ( [ PARTITION BY <expr1> ] ORDER BY <expr2> [ { ASC | DESC } ] )

SELECT emp_id, year, revenue, LEAD(revenue) OVER (PARTITION BY emp_id ORDER BY year) AS next_revenue FROM sales;

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: Snowflake runs on a continuously deployed, versionless engine, so minimum version information does not apply.

Official Documentation

For the authoritative spec, use the vendor docs. This page is the fast “sanity check”.

View Snowflake Documentation →

Looking for more functions across all SQL dialects? Visit the full SQL Dialects & Window Functions Documentation.