Mapping allows you to generate the corresponding database views during the modeling of the multi-dimensional model for a hierarchy. Changes in a model have an effect in another model as a result of mapping.
Prerequisites
Mapping is realized with engineering actions. An appropriate Java installation is required for the execution of engineering actions.
The "Business Intelligence – Multi-Dimensional Modeling" profile must be imported in the model with the database schema to which mapping takes place.
Function
You can generate database views in the database model for SQL Server from the multi-dimensional model. You can then work in both models.
The technical decision as to which mapping variant you choose depends mainly on the downstream analysis tool. While the third normal form remains close to the modeling, the denormalized and the tree structure variant are necessary for some analysis tools for simplification purposes, as only one database view needs to be evaluated.
Before you transfer changes from the multidimensional model to the database model with mapping, you can display them in a preview.
The mapping marks model elements in the database model as Created by Mapping and they have model references to the conceptual model so that you can always track which model elements have come from where.
Customizing
If you want to change the behavior of a mapping, because e.g.
- you have other rules for assigning names or
- you want to apply the mapping to other stereotypes or
- you want to create other model elements or
- you want to transfer other stereotype properties,
then you should create your own mapping using the model-to-model software development kit (M2M-SDK).
You can find more information about M2M SDK in the Transforming Models (M2M SDK) chapter in this Help.
Related Topics
This chapter contains the topics:
