Teradata BTEQ Script Sources > View results in Data Governance and Catalog > View data lineage
  

View data lineage

Data lineage is a visual representation of the flow of data across the systems in your organization. Lineage depicts how the data flows from the system of its origin to the system of its destination.
Data lineage views are available for technical assets in the catalog source. You can view lineage at the catalog source, data set, or data element level.
The lineage at the catalog source level shows how data flows from one catalog source to another. The lineage at the data set and the data element levels show how other technical assets such as files or tables contribute to the selected asset.
If linking catalog sources is available for your catalog source, you can use Metadata Command Center to generate data lineage based on rules or by generating automated lineage with CLAIRE. You can choose source and target catalog sources and objects to link and generate lineage.
To determine whether linking catalog sources is available for your catalog source, navigate to the Configuration tab of the Link Catalog Sources page. The catalog source must appear in the list of source and target catalog sources.
For information about linking catalog sources, see Link catalog sources.

View lineage at the catalog source level

The catalog source level shows how data flows from one catalog source to another with the lineage aggregating data from the data set and data element levels.
To view data lineage at the catalog source level, open a technical asset, click the Lineage tab, and then verify that the level is set to Catalog Source Level.

View lineage at the data set level

The data set level displays individual sets of data in the data flow.
To view data lineage at the catalog source level, open a technical asset, click the Lineage tab, and then verify that the level is set to Catalog Source Level.
The following image shows how a target CUST data set gets data from a CUSTOMER data set through a statement before connection assignment:
The data set level lineage diagram starts at a CUSTOMER data set that the Teradata BTEQ statement injects into the source CUST data set before connection assignment.
The following image shows how a target CUST table gets data from a CUSTOMER table through statements after connection assignment to a Teradata database source system with the Teradata BT_tduser_298 endpoint:
The data set level lineage diagram starts at a CUSTOMER table that the Teradata BTEQ statements merge into the source CUST table after connection assignment.

View lineage at the data element level

The data element level displays details of the data set level. At the data element level, you can see the input sources for expressions or commands and calculations or transformations on the data.
To view data lineage at the data element level, open a technical asset, click the Lineage tab, and then verify that the level is set to Data Element Level.
The following image shows how the target CUST table gets data from a CUSTOMER data set through a statement before connection assignment:
The data element level lineage diagram starts at a CUSTOMER data set that a Teradata BTEQ statement injects into a CUST data set before connection assignment.
The following image shows how the target customer_id column of the CUST table gets data from a CUSTOMER table through statements after connection assignment to a Teradata database source system with the Teradata BT_tduser_298 endpoint:
The data element level lineage diagram starts at a CUSTOMER table that Teradata BTEQ statements inject into a cust_id column of the CUST table after connection assignment.