Skip to content
Upstream

GUIDE, read 10 Nov 2026

Snowflake builds column lineage from its own query history, exposes it through Snowsight and GET_LINEAGE, and widens it through Horizon

The matrixAll guides

Three pieces share the name lineage

Snowflake uses lineage for three things that people often confuse. Snowsight has a lineage view. SQL has a function, GET_LINEAGE, that returns the same graph as rows. And the account usage view ACCESS_HISTORY records which objects and columns queries accessed. A fourth name, Horizon, is the umbrella for governance features that includes lineage.

Per Snowflake's docs, Horizon Catalog bundles sensitive data protection, data quality, end-to-end lineage and AI governance. Snowflake describes Horizon Catalog as an open, interoperable catalog for data inside or outside Snowflake. That framing matters when you ask what the lineage can see: the native graph sees Snowflake; the wider graph depends on connectors and events.

What the native graph records

Snowflake's lineage tracks data movement, such as CTAS, INSERT and MERGE statements, and object dependencies such as a view on a table. Snowsight can trace a column to all its upstream and downstream columns, with a distance value. Lineage is an Enterprise Edition (or higher) feature.

The graph comes from Snowflake's own query history. Snowflake says lineage began in November 2024 and is retained for one year, and that lineage captured before November 2024 for data movement is not available. A table loaded once in 2023 and not touched since can therefore have no data-movement edges in the native graph. Check this before you test with an old pipeline.

GET_LINEAGE puts the graph in SQL

GET_LINEAGE returns lineage for objects in domains COLUMN, TABLE, EXTERNAL and more, up to 10 million edge rows. Because it is a function, you can call it from a task, a test or a notebook, and join the result to your own tables of owners and tickets. That is the route to an automated impact check on Snowflake alone.

The Snowsight view shows lineage details according to the viewer's access control privileges, and lineage viewing can be delegated. Snowflake states that boundary for Snowsight. Check whether it holds for the function in your account, and test with the role your CI job or agent will use, not an admin role.

ACCESS_HISTORY records access, not lineage

ACCESS_HISTORY records objects, including columns, accessed within the last 365 days, and is available on Enterprise Edition. It answers a different question: who read which column, and when. It is the raw material that other tools mine. Collibra lists Snowflake (ACCESS_HISTORY) among its supported lineage sources. Atlan says its miners parse query history for Snowflake, BigQuery and Redshift to build lineage.

If you only need to know which role read a regulated column last month, ACCESS_HISTORY is the right source. If you need to know which downstream column was built from it, use the lineage graph. Mixing them up leads to the wrong audit evidence.

Documented limits of Snowflake lineage

Snowflake states several limits plainly. Read them as the shape of the feature.

  • Lineage excludes tables used only for joins or filters, so a lookup table that shapes the output without contributing a column does not appear.
  • Column lineage is not supported for semantic views.
  • Lineage is not available for objects in shared databases or the SNOWFLAKE database.
  • Data-movement lineage captured before November 2024 is not available, and retention is one year.

Horizon widens the graph beyond Snowflake

Horizon Context says it stitches lineage from query history, external query logs, BI systems and OpenLineage into one column-level graph. Snowflake accepts OpenLineage events over a REST endpoint, so tools like dbt and Airflow can add external lineage. Horizon metadata connectors, currently in Preview, collect from PostgreSQL, SQL Server, Tableau, Power BI and dbt.

On the matrix, Snowflake is marked partial for BI field lineage and for transformation logic. Tableau and Power BI are named as connectors, and Snowflake labels them Preview, so the BI hop is documented but not yet generally available as of the date read. Snowflake also describes semantic views that define business metrics, dimensions and relationships once for reuse.

Tags, masking and agents

Snowsight's lineage tab detects missing or mismatched tags on upstream and downstream columns and helps apply them. Tags are inherited down the object hierarchy and can be set to propagate automatically. For agents, Snowflake offers a Snowflake-managed MCP server with role-based access control, and says Snowflake enforces role access, masking and row-access policies when an AI agent queries data.

The strength here is that governance and lineage sit in the same system as the data. A tag, a masking policy and a lineage edge refer to the same object, with no sync job between them.

How Snowflake lineage compares

Snowflake's lineage is strongest where your estate is mostly Snowflake. The graph needs no connector, no agent and no extra credential, because the data is already in the account. It is weaker where the pipeline starts outside Snowflake or ends in a BI tool, which is where Horizon connectors and OpenLineage events are meant to fill in. Plan the test so that it crosses at least one of those boundaries.

A one-hour test shows how much of this applies to you. Run a CTAS from one table into another and open the column view in Snowsight. Then add a join to a lookup table that contributes no output column, and see whether the lookup appears. Call GET_LINEAGE for the same column from the role your automation uses. Finally, send one OpenLineage event for a dbt run to the REST endpoint and see whether the edge shows up beside the native ones. Four checks, and you know the real shape of the graph for your account. Write the results next to the documented limits so the next person does not repeat them.

No separate price was found for lineage or Horizon Catalog on Snowflake's pricing page (none found on 10 Nov 2026). Snowflake prices on consumption, with lineage in the Enterprise feature set. The table sets the pieces side by side.

PieceWhat it givesDocumented limit
Snowsight lineageColumn trace with distance value, tag mismatch detectionExcludes join-only and filter-only tables
GET_LINEAGERows for COLUMN, TABLE, EXTERNAL domains, up to 10 million edgesViewer privileges apply
ACCESS_HISTORYObjects and columns accessed in last 365 daysEnterprise Edition
OpenLineage endpointExternal lineage from dbt and Airflow over RESTDepends on the emitting tool
Horizon connectorsPostgreSQL, SQL Server, Tableau, Power BI, dbtPreview

Sources

  1. Snowflake: docs.snowflake.com/en/user-guide/ui-snowsight-lineage.md, read 10 Nov 2026
  2. Snowflake: docs.snowflake.com/en/sql-reference/functions/get_lineage-snowflake-core.md, read 10 Nov 2026
  3. Snowflake: docs.snowflake.com/en/sql-reference/account-usage/access_history.md, read 10 Nov 2026
  4. Snowflake: docs.snowflake.com/en/user-guide/snowflake-horizon/horizon-context.md, read 10 Nov 2026
  5. Snowflake: docs.snowflake.com/en/user-guide/object-tagging/introduction.md, read 10 Nov 2026
  6. Snowflake: docs.snowflake.com/en/user-guide/snowflake-horizon.md, read 10 Nov 2026
  7. Snowflake: docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp.md, read 10 Nov 2026
  8. Snowflake: docs.snowflake.com/en/user-guide/external-lineage.md, read 10 Nov 2026
  9. Snowflake: www.snowflake.com/en/pricing-options, read 10 Nov 2026
  10. Collibra: productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/r, read 10 Nov 2026
  11. Atlan: docs.atlan.com/product/capabilities/lineage/best-practices/capture-and-troublesh, read 10 Nov 2026

Last reviewed 10 Nov 2026.