7/29/2019 Line Item Dimension

1/2

Line item and high cardinality dimension

The info cube uses bit map index and the B tree index. The creation of the indices depends on

underlying database also. This document demonstrates and explains the indices which are created when

a line item dimension and the High cardinality dimension check boxes are selected while creating a

dimension in the cube.

Line Item dimension: If this check box is checked, it implies that only one characteristic can be added to

this dimension. Once a dimension becomes a line item, the system does not create a dimension table for

it and the SID table itself is used as the dimension table.

The Line item dimension is considered as high cardinality dimension and hence B-tree indices (non-

unique) are created it by the system by default. Though you get an option of high cardinality also in the

properties of the dimension but checking that does not make any difference, as a line item dimension is

meant to handle a high cardinality.

High cardinality dimension: Checking this check box tells the system that this dimension has high

cardinality and the system creates a B-tree index for this, as B tree index is more suited in high

cardinality than the Bitmap index which the system generates by default and uses for general

dimensions.

Following are certain scenarios in which the Bit map and B tree indices are created:

1. If nothing is done to the dimensions, i.e. no LID and the HCD is selected: The system generates theBitmap index in Oracle and B-tree Index in MS SQL server for the fact tables.

Dimension tables:

B-tree (Unique)primary index in Oracle

B-tree (non-unique)-secondary Index in Oracle

B-tree (Unique, clustered) - Primary index in MS SQL

B-tree (non-unique, non-clustered)- secondary index in MS SQL

2. If you check the Line item dimension only: The system generates the B tree (non-unique) index in

Oracle and B-tree (Non unique and non-clustered)

3. If both the LID and the HCD are checked: The system generates B-tree index. Checking both does not

have any effect on the type of index created.

7/29/2019 Line Item Dimension

2/2

DIMENSION TABLE:

DIMID SID_GLacnt Sid_pr_ctr Sid_func_ar

15 35 89 48

17 37 87 41

SID TABLE:

SID OBJERVS /BIC/GLACNT /BIC/ACNT_GRP

0 A 10000278 8000

1 A 10000899 8000

BITMAP INDEX

B-TREE INDEX (UNIQUE)

B-TREE INDEX (NON-UNIQUE)

ORACLE

B-TREE INDEX (NON-CLUSTERED, NON-UNIQUE)

B-TREE INDEX (CLUSTERED, UNIQUE)

MS SQL SERVER

KEY_Z_CUBEP KEY_Z_CUBET KEY_Z_CUBEU Key_z_cube1 Key_z_cube2 /BIO/Deb_cred_lc

5 900 0 9 15 2000

5 950 0 10 17 -38878

Line item Dimension

FACT TABLE: