Before you begin, you must complete Exercise 4: Transforming the logical data model to a physical data model.
In this exercise, you will modify the properties of a generalization object in the HR.ldm logical data model, then transform again to a physical data model. You will then observe how the changes to the generalization object properties affected the transformation.
To modify transformation properties to roll up:
This link represents a relationship called a generalization. A generalization is a relationship that can only be created by using the diagram editor.
On the General tab in the Properties view, you can see that the Transform as property is set to Separate Table. This explains why the diagram under HR.dbm you saw in the last exercise has four tables, mapping closely to the four entities in HR.ldm, because these entities are set to transform as separate tables. The Separate Table option is used for a normalized design.
In this case, specify HR_rollup_pdm as the name for the new physical data model file, and HR_rollup as the schema name.
Notice the differences between this physical data model and the one that was created in the last exercise. In this case, the REGULAR and HOURLY tables were not created, and the EMPLOYEE table has more columns and a foreign key mapping to table EMPLOYEETYPE. The Roll Up option is used for one type of denormalized pattern.
Now you are ready to begin Exercise 6: Modifying transformation properties to roll down.