DataStore Object Settings 

Use

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 data in the DataStore object.

More information: Standard DataStore Objects, DataStore Objects for Direct Update, and Write-Optimized DataStore Objects

Type-Specific Settings

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

For Write-Optimized DataStore Objects

Do Not Check Uniqueness of Data

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 you set this indicator, 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:

Generation of SID Values

With the Generation of SID Values indicator, you specify whether SIDs are created for the new characteristic values in the DataStore object when the data is activated. If you do not set the indicator, no SIDs are created and activation is completed faster.

Loading Unique Data Records

If you are only loading unique data records (data records with nonrecurring key combinations) into the DataStore object, the loading performance improves if you set the Unique Data Records indicator in DataStore object maintenance.

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 terminates the process. Check whether the DataStore object might be write-optimized.

Automatic Further Processing

If you are using a 3.x InfoPackage to load data, you can activate several automatic functions 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 automatic functions.

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 of the data to OK after the data has been loaded into the DataStore object. Activate 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 that has the quality status OK is transferred from the activation queue into the table of active data, and that the change log is updated. Activation is carried out by a new job that is started after data has been loaded into a DataStore object. If the activation process terminates, there can be no automatic update.

●      Updating Data from DataStore Objects Automatically

Using this indicator, you can specify that the DataStore object data is automatically updated. Once the data has been activated, it is updated to the connected InfoProviders. The first update is automatically an initial 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.

 

Only switch on automatic activation and automatic update if you are sure that these processes do not overlap.

You can find more information about setting under Runtime Parameters of DataStore Objects and Performance Optimization for DataStore Objects.