Lineage Overview for Models

You may even use the lineage overview on models not in the current configuration using the MANAGE > Repository function.

The Data Flow Overview lineage (see TYPE in the upper right of diagram) has a very limited scope, only to the specific subset that is a self-contained model, e.g., a schema model in a database model or a transformation model or connection model in an ETL/DI model or BI model. Thus, it has none of the information determined in an Impact or Lineage trace diagram, so that connections are not resolved (may just be a * because of “Select *” in the connection definition). To get a true lineage picture you must use the Impact or Lineage trace from a table or column (field).

In addition, in the Overview lineage of a connection model in an ETL/DI model or BI model, many of the object are not even included in an end-to-end lineage trace and thus you will not be able to trace from that object at all. This limitation is caused by the fact that connection definitions themselves only show in the overview and are not a part of a lineage trace and thus there is no way to trace lineage from them.

The data flow overview lineage presents detailed transformation lineage vs. a lineage trace which presents summary lineage.

In particular, when you select a runtime job, and go to the data flow tab, you see the detailed transformation lineage: every transformation is being depicted on the screen. This view is good as long as you only look at one job at a time.

Finally, the Data Flow presentation for overview lineage does notoffer the Tree tab as the scope is only the currently model and the Tree tab features end-to-end lineage, which is not available for overview lineage presentations.