Related link: Cube Load with Drillthrough
The cube load writes data in a cube on the Jedox In-Memory DB server. 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 OLAP 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 server|
|Target Cube:||Cube in the Jedox In-Memory DB server|
The load mode is selected depending on the existing structures and data in the target system. 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 What is Splashing?
|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.
|none:||Columns of source and dimensions of cube have to match exactly. (default)|
|noneWithDefaultWrite:||If dimensions of the cube are not in the source, the values are written to the Default Write Element of the dimension. The cube layout is not changed.|
|addDimensions:||If columns in the source are not in the cube, they are added as cube dimensions at the end. If dimensions of the cube are not in the source, the values are written to the Default Write Element of the dimension.|
|updateDimensions:||The cube layout is modified exactly to the columns of the source. Note that dimensions may be removed from the cube, in which case the Default Read Element of the dimension is used and no data is lost.|
|reorderDimensions:||The columns of the source and the dimensions of the cube have to match, but not the order. If the order does not match, the ordering of the cube is changed.|
Deactivate while Loading:
|Cube Access:||This option can only be used in load mode “insert”. If activated, then the data cube is locked for read and write access for all other In-Memory DB users. With this option you can prevent seeing inconsistent cube values during the cube load.|
|Rules Calculation:||The calculation of rules in the In-Memory Database can be deactivated for this cube during the load. It may have a positive influence on rules with markers only when loading to consolidated cells.|
The Supervision Server (SVS) event initCubeWorker, which is executed at changes of cell values in a cube, can be deactivated for the cube during the load. See article Supervision Server Handlers for detailed information on this event.
|Bulk Size:||Size of blocks for In-Memory DB server write requests.
If this field is filled with a value, this value will be used. If this field is empty, the value of the key “integrator.loads.cube_bulk_size” in “Administration – Settings” will be used in the case that the value is greater than 100,000.
|Settings for Drillthrough||See article Cube Load with Drillthrough.|
|Settings for Semi-additive Measures||For the use of semi-additive measures, especially for time-dimensions, the dimensions for measure declaration and for semi-additive aggregations can be defined here.|