Related link: Cube Load with Drillthrough
The cube load writes data in a cube in the Jedox In-Memory DB (OLAP). If the cube is not yet present in the database, it will be created during the load. In this way, the modeling can be carried out within Jedox Integrator. A complete database can even be created from scratch.
The source is an extract or transform that defines in its rows the data to be written to the cube. The first columns of the source must contain the names of the dimension elements of the cube (except in delete mode; see mode explanations below). The last column contains the value that is written in the cube cell.
In the following example, the cube has eight dimensions, one less than the number of columns in the source:
|Target Connection:||Connection to a Jedox In-Memory DB|
|Target Cube:||Cube in the Jedox In-Memory DB|
The load mode selected depends on the existing structures and data in the target system. This field is required. Cube load modes are:
Can be set to write on consolidated elements. Possible values are:
The Splash mode is set to “disabled” unless otherwise indicated. Splash modes “add” and “set” are only possible in combination with load modes “insert” and “delete”. Further information on the topic of splashing can be found in the article Splashing: Data Entry on Consolidated Cells
|Handling of missing elements:||
In general, if you write data to a cube cell, the dimension elements of the cell path must exist for all dimensions. You can configure how the cube load should react if this is not the case for one (or several) dimensions:
With options mapToDefault and createUnderDefault you will not lose the values of items which do not exist in the dimension. The default element is the same for all dimensions and has to exist before the load for all dimensions for which this logic should apply.
In the Dimension Mapping table, any dimension of the cube can be assigned for each source column. For columns that should not be loaded to the cube, the entry “” is used. Thus it is possible to rename and skip columns. The dimension order cannot be changed, which is only relevant if the cube does not yet exist. The last source column is not displayed in the Dimension Mapping, as it always contains the cube cell value.
By default, if no Dimension Mapping is given, the names of the cube dimensions are entirely defined by the names of the source column names. In this case, the number of dimensions must be equal to the number of columns in the source minus 1.
|Cube Layout Change Mode:||
This option defines the behavior if the source columns and the cube layout don’t match for load modes “add”, “insert”, and “update”. It allows writing to a default element for missing source columns and the automatic change of the cube layout before the data is loaded.
Deactivate while Loading:
Size of blocks for OLAP write requests:
|Settings for Drillthrough||Default setting is None. For details on drillthrough options, see Cube Load with Drillthrough.|
|Settings for semi-additive measures||For the use of semi-additive measures (especially time dimensions), you can define the dimensions for measure declaration and for semi-additive aggregations here.|