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 transactional is only intended for special cases. You can switch the type as long as there is still no data in the DataStore object.

See also Standard DataStore Objects DataStore Objects for Direct Update and Write-Optimized DataStore Objects.

Check Table for the InfoObject

Here the name of the InfoObject is displayed for which the DataStore object is also the check table, if necessary. You can specify this when creating an InfoObject. See also Tab Page: Master Data/Texts in the InfoObject maintenance.

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 folder Semantic Key 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 und there can be more than one record 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. If the indicator is not set, no SIDs are created and activation is completed faster.

Loading Unique Data Records

If you only load unique data records (meaning data records with nonrecurring key combinations) into the DataStore object, then the loading performance is improved when you set the indicator Unique Data Records in the DataStore object maintenance.

The records are then updated more quickly because the system no longer needs to check whether the record already exists. You do have to be sure that there duplicate records are definitely not being loaded, because this will lead to termination.

If you set this indicator, the indicator for creating SID values is automatically set as well.

This is no longer supported for new DataStore objects. It is therefore only displayed in the maintenance dialog (UI) for existing objects, where it was set in earlier releases.

Automatically Setting Quality Status to OK

With this indicator, you can determine 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.

Automatically Activating the DataStore Object Data

With this indicator, you can establish that the data that has Quality Status OK be 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.

Automatically Updating Data from the DataStore Object

With this indicator, you can establish that the DataStore object data be automatically updated. Once it has been activated, the data 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.

 

Only activate automatic activation and updating if you can ensure that these processes do not overlap.

If you use process chains to guarantee serial processing of the process, these settings are not supported. Then you have to include the automatic processes as process types in the process chain.

See also the example for Including DataStore Objects in Process Chains.

For further settings see Performance Optimization for DataStore Objects.