Lineage across the model
Lineage traces the path data takes through the modelled system, so an attribute can be followed from where it originates to everywhere it is consumed.
Impact analysis on a proposed change
Impact analysis takes a change you are considering and reports what it touches. That converts a schema alteration from a judgement call into a list you can review and size.
Mapping and environment comparison
Source→Target Map records how fields move between systems, with transformation notes. Env Compare shows where two environments have drifted apart, which is usually the first thing worth knowing when something works in one and not the other.
What this covers in the product
Every capability below is part of this area of Yantra Studio.
- Data Manager
- Source→Target Map
- Lineage
- Impact Analysis
- Env Compare
Questions
Is lineage derived or entered?
It comes from the modelled relationships and mappings, so it stays consistent with the model rather than being maintained separately.
Can I compare two environments?
Yes. Env Compare reports the structural differences between them.
Does impact analysis cover downstream reports?
It covers what is represented in the model — the further your source-to-target mappings extend, the further the analysis reaches.
Related capabilities
-
The diagram and the data model are one artefact
Model entities, attributes and relationships once: the diagram and the data model are one artefact, with subject areas, a metadata repository and normal-form checks.
-
One agreed meaning per term
Keep an agreed business glossary and a data dictionary attached to the model, and export the dictionary to Excel for people who will not open the tool.
-
DDL and migrations, generated from the model
Export PostgreSQL, MySQL, BigQuery and SQL Server DDL from your data model, and generate delta migration scripts from the difference between two versions.