A data movement model (DMM) provides a global view of the movement of information in your organization. You can analyze and document where your data originates, where it moves to, and how it is transformed on the way, including replications and ETL.
-
Data movement diagram (see Data Movement Diagrams) allows you to model:
-
Data replication – lets you describe and configure replication processes where a source database is replicated into one or more remote databases via replication engines. You can generate and reverse engineer Replication Server® files.
-
Data transformation – shows a high-level view of a data transformation, where data from diverse sources are combined to be loaded to output sources via ETL (Extract Transform and Load) and EII (Enterprise Information Integration). The transformations are modeled in more detail in data transformation and transformation control flow diagrams.
-
-
Data transformation diagram - lets you detail how data is extracted from data inputs, transformed by actions, and loaded into data outputs (see Data Transformation Diagrams).
-
Transformation control flow diagram - lets you represent a sequence of data transformations (see Transformation Control Flow Diagrams).
The following example shows how the various diagrams work together when modeling a data transformation. The data movement diagram contains the transformation process with its input and output sources. You can build one or more data transformation diagram(s) to detail your transformations, and a transformation control flow diagram to show the order in which these transformations are executed:
