...
The structure of a dimension level table depends on whether the dimension level is the highest (i.e., most coarse-grained) level of the dimension. If it is not the highest dimension level, the table has a unique id column (used for referencing), a value column (holding a representation of the attribute's value), a description column (providing a more verbose textual description of the value), and a parent_id column holding a foreign key reference to the id of the parent dimension level value. The latter can be omitted for the highest level of a dimension, because this does not have a parent. The following table gives an overview of the columns of a dimension level table.
| Column Name(s) | Type | Cardinality | Description |
|---|---|---|---|
| id | arbitrary | 1 | id of dimension value, must be unique |
| value | arbitrary | 1 | representation of dimension level value |
| description | nvarchar/varchar2 | 1 | textual description of the dimension level vale |
| parent_id | arbitrary | 0...1 | foreign key reference to the table of parent dimension level, can be omitted if no parent exists |
Interactive PMCube Explorer provides a set of tools that support the creation of the data cube and the integration of data. With the Meta-Data Editor, you can create a meta-data file from scratch. The Data Integration Wizard helps you to create a data cube from an event log file and integrate its data into the cube. You can find the data integration tools on the Tools tab of the application's ribbon menu.