Model lineage describes the relationships between data objects and displays how data moves and connects within a model. It helps you understand where data originates, how it is structured, and which objects depend on it.
In Quest Data Modeler, model lineage covers relationships among entities, attributes, tables, columns, views, and materialized views within a model, depending on your database platform and the objects available in the model.
Why Model Lineage Matters
Understanding lineage helps both business and technical users:
-
Assess the impact of a change before modifying an object
-
Trace the source of a data quality issue back to its origin
-
Build trust in reports and models by confirming where data originates
-
Support governance, compliance, and audit requirements by showing how data flows through and across models over time
How Lineage Is Represented
Lineage between tables and columns is derived from the relationships and keys defined in the model. When two tables are related through a key, QDM uses that relationship to trace how data connects and flows between them.
Lineage can be traced horizontally and vertically:
-
Upstream: Traces dependencies backward to identify the source tables or columns that a given table or column depends on
-
Downstream: Traces dependencies forward to identify the tables or columns that depend on a given table or column
-
Vertical: Traces how objects and models have evolved over time by showing lineage events such as import, derivation, and reverse engineering
Note: Model lineage is supported for conceptual, logical, and physical models. In conceptual models, lineage is available at the entity level. In logical models, lineage can be viewed at the entity and attribute levels. In physical models, lineage can be viewed at the table and column levels, providing detailed traceability across implemented data assets.
For more information about the Model Lineage feature, which enables lineage tracing within a model, refer to the View and Trace Lineage topic.