Advanced Data Modeling

Heterogeneous Mapping Heterogeneous Mapping is the ability of MSTR7 tools to join on unlike column names. Heterogeneous Mapping is the ability of MSTR7 tools to join on unlike column names.ORDER_DETAIL Order_ID Call_Ctr_ID Order_Date LU_DATE Date_ID Month_ID Quarter_ID

Attribute Forms A Form is a logical representation of an Attribute. Every Attribute is defined by at least one Form. A Form is a logical representation of an Attribute. Every Attribute is defined by at least one Form. Multiple DESC columns can now be displayed under the same attribute. Multiple DESC columns can now be displayed under the same attribute.

Attribute Display Different combinations of forms can be used to display an attribute on report or while browsing in Data Explorer. Different combinations of forms can be used to display an attribute on report or while browsing in Data Explorer.

Simple Attributes The Attributes that we have created up to this point are simple – each of them is based on a real column name in the database. The Attributes that we have created up to this point are simple – each of them is based on a real column name in the database.

Derived Attributes Derived Attributes are based not only on a single column name, but on operations between multiple columns or anything meaningful to the database. Derived Attributes are based not only on a single column name, but on operations between multiple columns or anything meaningful to the database. I.e. Customer Age can be defined as “Today”- customer birth date. I.e. Customer Age can be defined as “Today”- customer birth date.

Implied Attributes Implied Attributes are not explicitly present in terms of columns in the DW, but are implied by the existence of a particular table. Implied Attributes are not explicitly present in terms of columns in the DW, but are implied by the existence of a particular table.RUSH_ORDER Order_ID Customer_ID Emp_ID Order_Date Order_amt Rush_Charge Ship_Charge Amt_Paid (Rush_Order) Y for every row

Implied Attributes Example: when an order is rushed, a new record is made in the rush_order table to store extra facts associated with rushed orders. The nature of the table implies that a certain attribute or fact is present, but because it would have the same value for all rows, the column is not included in the schema. Therefore, the Rush_Order attribute is defined with a constant “Y” instead of a column definition. Example: when an order is rushed, a new record is made in the rush_order table to store extra facts associated with rushed orders. The nature of the table implies that a certain attribute or fact is present, but because it would have the same value for all rows, the column is not included in the schema. Therefore, the Rush_Order attribute is defined with a constant “Y” instead of a column definition. In the past, such attributes required dummy columns or views in the database. In the past, such attributes required dummy columns or views in the database.

Compound Attributes A Compound Attribute is an attribute with a compound primary key (more than one ID column is specified as the ID). More than one ID is needed to uniquely identify the Elements of that Attribute. A Compound Attribute is an attribute with a compound primary key (more than one ID column is specified as the ID). More than one ID is needed to uniquely identify the Elements of that Attribute.

Joint Child Relationships Joint Child Relationships exist when one Attribute is a parent of a combination of children Attributes Joint Child Relationships exist when one Attribute is a parent of a combination of children Attributes Promotion QuarterItem ProductTime Promotion

Joint Child Relationships Attributes typically belong to only one hierarchy. However, in the example above, the attribute Promotion relates to a combination of children attributes from different hierarchies. A promotion ties directly to a particular item at a particular point in time (in this case, quarter). So, for example, a lawn mower (item) might be associated with the Spring Readiness Sale (promotion) during Q (quarter). Attributes typically belong to only one hierarchy. However, in the example above, the attribute Promotion relates to a combination of children attributes from different hierarchies. A promotion ties directly to a particular item at a particular point in time (in this case, quarter). So, for example, a lawn mower (item) might be associated with the Spring Readiness Sale (promotion) during Q (quarter). Joint Child Relationships must be specified in the Attribute Editor; they cannot be specified in the Attribute Creation Wizard. Joint Child Relationships must be specified in the Attribute Editor; they cannot be specified in the Attribute Creation Wizard.

Steps ahead Modeling Workshop Part 2. Modeling Workshop Part 2.