Tutorials: Documenting Data Lineage
Go Up to Introduction
The Data Lineage feature of ER/Studio Data Architect enables you to document the movement of data from point A to point B (and any intermediate steps in between). This movement is sometimes referred to as Extraction, Transformation and Load (ETL). Points A and B can be anything from flat files, high-end databases such as Oracle and DB2, XML, Access databases, and Excel worksheets. This is sometimes referred to as source and target mapping. A model produced in ERStudio can represent any point along the way. Data Architects need the ability to specify the source or target of data down to the column-level. Along with the metadata that defines the source and target mapping are rules for how the data is manipulated along the way.
The next section will help you document the data lineage of your systems.
It is comprised of the following tasks which correspond to the general ETL workflow:
- Creating a Data Flow
- Creating a Data Movement Rule
- Defining External Source and Target Systems
- Creating a Data Lineage and Transformation Visualization