# Unity Catalog lineage, defined with a sourced example

GLOSSARY, read 10 Nov 2026

**The short answer.** The lineage Databricks captures for tables registered in Unity Catalog. It records table and column links from queries, and the jobs, notebooks and dashboards that touch them. It is exposed in Catalog Explorer, system tables and an API. Databricks stores lineage in system tables named system.access.table_lineage and system.access.column_lineage.

## Definition

The lineage Databricks captures for tables registered in Unity Catalog. It records table and column links from queries, and the jobs, notebooks and dashboards that touch them. It is exposed in Catalog Explorer, system tables and an API.

## Example from a real tool

**Example.** Databricks stores lineage in system tables named system.access.table_lineage and system.access.column_lineage.

## Related terms

- [tag propagation](/glossary/tag-propagation/): Copying a tag, such as PII, from one asset to the assets built from it along lineage links.
- [semantic layer](/glossary/semantic-layer/): A shared set of business definitions, such as metrics and dimensions, that sits between raw tables and the tools that query them.
- [GET_LINEAGE](/glossary/get-lineage/): A Snowflake SQL function that returns upstream or downstream lineage for an object.

## Where to read more

- [The Lineage Depth Matrix](/matrix/)
- [All glossary terms](/glossary/)

## Sources

- docs.databricks.com/aws/en/admin/system-tables/lineage: https://docs.databricks.com/aws/en/admin/system-tables/lineage (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://datalineagecompare.com/glossary/unity-catalog-lineage/
