Table of Contents

Search

  1. Preface
  2. Understanding the Repository
  3. Using the Repository Manager
  4. Folders
  5. Managing Object Permissions
  6. Local and Global Shortcuts
  7. Team-Based Development with Versioned Objects
  8. Labels
  9. Object Queries
  10. Team-Based Development with Deployment Groups
  11. Copying Folders and Deployment Groups
  12. Exporting and Importing Objects
  13. Exchanging Metadata
  14. Copying Objects
  15. Metadata Extensions
  16. Appendix A: MX Views Reference

Repository Guide

Repository Guide

Working with Star Schemas

Working with Star Schemas

Use PowerCenter to create a star schema of fact and dimension tables. You can create these definitions in the Target Designer, or you can use the mapping wizards. When you export relational target definitions in a star schema to a third-party tool, by default, MIMB does not store the dimensional role of each definition, such as fact or dimension.
You can create user-defined metadata extensions in the source and target definitions to define the dimensional role of each definition. When you export source and target definitions with these user-defined metadata extensions, MIMB converts the information in the metadata extensions to dimensional role information in third-party tools that work with dimensional metadata, such as IBM DB2 Cube Views.
Also, when you import metadata into PowerCenter from a third-party tool that works with dimensional metadata, MIMB converts the dimensional information into user-defined metadata extensions in PowerCenter.
The following table lists the metadata extension names and values that MIMB uses when you export and import dimensional metadata:
Metadata Extension Name
Possible Metadata Extension Values
DimensionalRoleType
UNDEFINED
FACT
DIMENSION
OUTRIGGER
BRIDGE
HIERARCHY_NAVIGATION
DimensionalType
FIXED
TYPE_1
TYPE_2
TYPE_3
Not all third-party tools that work with dimensional metadata support all dimensional role and dimensional type values.
For example, you have the following relational target definitions with metadata extensions in PowerCenter:
Target Name
Metadata Extension Name
Metadata Extension Value
Customer
DimensionalRoleType
FACT
CustAddress
DimensionalRoleType
DIMENSION
CustPhone
DimensionalRoleType
DIMENSION
You export the target definitions to IBM DB2 Cube Views. You import the PowerCenter metadata into Cube Views. Cube Views imports the Customer table as a fact table, and the CustAddress and CustPhone tables as dimension tables.

0 COMMENTS

We’d like to hear from you!