Data Catalog is deprecated and will be discontinued on January 30, 2026. For steps to transition your Data Catalog users, workloads, and content to Dataplex Universal Catalog, see Transition from Data Catalog to Dataplex Universal Catalog.
Stay organized with collections
Save and categorize content based on your preferences.
Data lineage lets you
track how data moves through your systems: where it comes from, where it is
passed to, and what transformations are applied to it.
When you use data lineage
with Data Catalog, be aware of the differences that are described in
this document.
For detailed information
about data lineage, see
About data lineage in the
Dataplex Universal Catalog documentation.
Enable data lineage
To use data lineage with Data Catalog, in the project
where you view lineage, enable the Data Catalog API and the
Data Lineage API.
IAM roles
To use data lineage with Data Catalog, you must be
granted the
Data Catalog Viewer role (roles/datacatalog.viewer)
to access the Data Catalog entry,
instead of the
Dataplex Catalog Viewer role (roles/dataplex.catalogViewer).
Other required roles to view lineage and manipulate lineage information are the
same as when using data lineage with
Dataplex Universal Catalog. For more information, see
Predefined roles for data lineage.
Limitations
For entries that were created in Data Catalog,
the Google Cloud console shows detailed information about the source and
target using the Data Catalog entry.
For entries that were created in Dataplex Universal Catalog, the
Google Cloud console doesn't show detailed information if there isn't an
equivalent Data Catalog entry.
Locations
Data lineage for Data Catalog entries is
available in the same
Dataplex Universal Catalog locations that
data lineage for Dataplex Universal Catalog entries is
available. In addition, data lineage for Data Catalog
entries (but not for Dataplex Universal Catalog entries) is available in
the following multi-regions:
asia (Asia)
eu (Europe)
us (US)
Billing impact
When you enable Data Lineage API on a project, review
the impact on your billing charges since Data Lineage API is enabled
on a per-project basis.
For multi-regions, such as European Union (eu), Asia (asia),
and United States (us), and for BigQuery Omni, lineage processing
is distributed to specific regions, and costs depend on the regions where
the processing is performed.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[[["\u003cp\u003eData lineage tracks the movement and transformations of data across systems, including its origin and destination.\u003c/p\u003e\n"],["\u003cp\u003eWhile data lineage integration with Data Catalog is deprecated, it is generally available with Dataplex Catalog, allowing you to track lineage for both entry types.\u003c/p\u003e\n"],["\u003cp\u003eEnabling the Data Lineage API is done on a per-project basis, automatically reporting lineage information for multiple Google Cloud services within that project.\u003c/p\u003e\n"],["\u003cp\u003eTo access data lineage with Data Catalog, you must be granted the Data Catalog Viewer role, whereas other lineage roles remain consistent with Dataplex Catalog usage.\u003c/p\u003e\n"],["\u003cp\u003eData lineage for Data Catalog entries is available in the same Dataplex locations, with added multi-region support in Asia, Europe, and the US.\u003c/p\u003e\n"]]],[],null,["# About data lineage in Data Catalog\n\nData lineage lets you\ntrack how data moves through your systems: where it comes from, where it is\npassed to, and what transformations are applied to it.\n| **Note:** Data lineage integration with Data Catalog is deprecated, but [data lineage integration with Dataplex Universal Catalog](/dataplex/docs/about-data-lineage) is generally available. You can track lineage for both Data Catalog entries and Dataplex Universal Catalog entries.\n\nWhen you use data lineage\nwith Data Catalog, be aware of the differences that are described in\nthis document.\n\nFor detailed information\nabout data lineage, see\n[About data lineage](/dataplex/docs/about-data-lineage) in the\nDataplex Universal Catalog documentation.\n\nEnable data lineage\n-------------------\n\nTo use data lineage with Data Catalog, in the project\nwhere you view lineage, enable the Data Catalog API and the\nData Lineage API.\n| **Caution:** Data lineage is enabled on a per-project basis, not a per-service basis. After you enable the Data Lineage API, lineage information is automatically reported for multiple Google Cloud services in the project, depending on their product-level lineage control. For more details, see [Data lineage considerations](/dataplex/docs/lineage-considerations).\n\nIAM roles\n---------\n\nTo use data lineage with Data Catalog, you must be\ngranted the\n[Data Catalog Viewer role](/iam/docs/understanding-roles#datacatalog.viewer) (`roles/datacatalog.viewer`)\nto access the Data Catalog entry,\ninstead of the\n[Dataplex Catalog Viewer role](/iam/docs/understanding-roles#dataplex.catalogViewer) (`roles/dataplex.catalogViewer`).\nOther required roles to view lineage and manipulate lineage information are the\nsame as when using data lineage with\nDataplex Universal Catalog. For more information, see\n[Predefined roles for data lineage](/dataplex/docs/iam-roles#lineage-roles).\n\nLimitations\n-----------\n\n- For entries that were created in Data Catalog, the Google Cloud console shows detailed information about the source and target using the Data Catalog entry.\n- For entries that were created in Dataplex Universal Catalog, the Google Cloud console doesn't show detailed information if there isn't an equivalent Data Catalog entry.\n\nLocations\n---------\n\nData lineage for Data Catalog entries is\navailable in the same\n[Dataplex Universal Catalog locations](/dataplex/docs/locations) that\ndata lineage for Dataplex Universal Catalog entries is\navailable. In addition, data lineage for Data Catalog\nentries (but not for Dataplex Universal Catalog entries) is available in\nthe following multi-regions:\n\n- `asia` (Asia)\n- `eu` (Europe)\n- `us` (US)\n\n| **Important:** Data Catalog **does not** guarantee higher availability or reliability for multi-regions compared to other Google Cloud regions. Multi-regions should be treated just like other [regions](/docs/geography-and-regions#regions_and_zones).\n\nBilling impact\n--------------\n\nWhen you enable Data Lineage API on a project, review\nthe impact on your billing charges since Data Lineage API is enabled\non a per-project basis.\n\nFor multi-regions, such as European Union (`eu`), Asia (`asia`),\nand United States (`us`), and for BigQuery Omni, lineage processing\nis distributed to specific regions, and costs depend on the regions where\nthe processing is performed.\n\nWhat's next\n-----------\n\n- [Use data lineage with Google Cloud systems](/dataplex/docs/use-lineage)\n- [Track data lineage for a BigQuery table](/dataplex/docs/track-lineage-quickstart)"]]
