Have ERwin support that more than 1 table in a target model can be linked to one and the same table in the source model.
I am working in an environment where one Logical model is supporting 2 physical environments: one "classic" (normalized) data model (in Oracle), and a Data Vault model in another (MS SQL Server) environment.
Working with 2 physical implementations is supported by Design Layers: one central model from which both the Oracle model and the MS SQL Server model are derived.
Of course I need to synchronize these 2 models when changes are applied to the Logical model. In the normalized environment this works fine, since mostly there is 1:1 relation between source model and target model.
However, the nature of a data vault is such that all entities are divided over at least 2 tables. When you are not familiar you look at this as vertical partitioning:
- when source table S1 has 6 columns, A, B, C, D, E and F
- then target table T1 is used for col A, B and C
and target table T2 is used for col D, E and F.
In other words: one table in the central source (Logical) model leads on average to one table in the Oracle environment, and at the same time to several (at least 2) tables in the MS SQL server environment.
ERwin only support a transformation which splits one table into 2 tables - but this is a one time thing, and the source table does not exist anymore after the fact. It appears that my real world scenario is not supported by current ERwin functionality. (and yes, dynamic transformations did exist until ERwin R7 or so)
Please sign in to leave a comment.