Show TOC

Function documentationDataStore Object Settings Locate this document in the navigation structure

 

When creating and changing a DataStore object, you can make the following settings:

DataStore Object Type

Select the DataStore object type. You can choose between Standard, Direct Update, and Write-Optimized, where Standard is the default value and Direct Update is only intended for special cases. You can switch the type as long as there is still no in the DataStore object yet.

More information: DataStore Object Types

Type-Specific Settings

The following settings are only available for certain DataStore object types:

For Write-Optimized DataStore Objects:

Allow duplicate data records

This indicator is only relevant for write-optimized DataStore objects. With these objects, the technical key of the active tables always consists of the fields Request, Data Package, and Data Record. The InfoObjects that appear in the maintenance dialog in the Semantic Key folder form the semantic key of the write-optimized DataStore object.

If this indicator is set, no unique index is generated with the technical name "KEY" for the InfoObjects in the semantic key and there can be multiple records with the same key in the active table of the DataStore object.

For Standard DataStore Objects:

Creating SID values

With the Generation of SID Values indicator, you define if SIDs are created for the new characteristic values in the DataStore object when the data is activated.

There are three options:

  • During Reporting: When data is activated in the DataStore object, no SIDs are retrieved for the new characteristic values. This reduces the runtime during activation. The SIDs are generated during query execution.

  • During Activation: The SIDs are generated already during the activation of the data. This reduces the runtime during query execution.

  • Never Generate SIDs: SIDs are never generated.

    This option makes sense for all DataStore object that are basically used for further processing in other DataStore objects or InfoCubes. If you create a query for a DataStore object with this property, the query cannot be executed. You can still define InfoSets with this DataStore object and execute queries for it.

Loading Unique Data Records

If you only load unique data records (data records with nonrecurring key combinations) into the DataStore object, the performance is improved when you set the Unique Data Records indicator in DataStore object maintenance. This setting is displayed as the default setting during the activation of data in administration or the corresponding process in the process chain. However, you can also overwrite this setting there, if the need arises (for example, for the initial loading of data).

The records are then updated more quickly because the system no longer needs to check whether the record already exists. You have to be sure that no duplicate records are loaded because this leads to termination. Check whether the DataStore object might be write-optimized.

Automatic Further Processing

If you still use a 3.x InfoPackage to load data, you can activate several automatisms to further process the data in the DataStore object. If you use the data transfer process and process chains that we recommend you use, you cannot use these automatisms.

We recommend that you always use process chains.

More information: Including DataStore Objects in Process Chains

Settings for automatic further processing:

  • Automatically Setting Quality Status to OK

    Using this indicator, you can specify that the system automatically sets the quality status to OK after loading data into the DataStore object. You should turn on this function. You should only deselect this indicator if you want to check the data after it has been loaded.

  • Activating the DataStore Object Data Automatically

    Using this indicator, you can specify that data, which has Quality Status OK, is transferred from the activation queue into the active data table, and that the change log is updated. Activation is carried out by a new job that is started after loading into a DataStore object is complete. If the activation process terminates, there can be no automatic update.

  • Updating Data from the DataStore Object Automatically

    Using this indicator, you can specify that the DataStore object data is automatically updated. Once the data has been activated, it is updated in the relevant InfoProviders. An initial update is carried out automatically with the first update. If the activation process terminates, there can be no automatic update. The update is carried out by a new job that is started once activation is complete.

    Note Note

    Only activate automatic activation and update if you can be sure that these processes do not overlap.

    End of the note.

For further settings see Performance Tips for DataStore Objects.

Runtime Parameters of DataStore Objects