Performance Tips for DataStore Objects 

Use

To ensure a satisfactory level of activation performance for DataStore objects, we make the following recommendations:

...

Generation of SID Values

It takes a long time to generate SID values and can be avoided in the following cases:

●      The Generation of SID Values flag should not be set if you are using the DataStore object for data storage purposes only. If you do set this flag, SIDs are created for all new characteristic values.

●      If you are using line items (document number or time stamp for example) as characteristics in the DataStore object, set the flag in characteristic maintenance to show that they are Attribute Only.

SID values can be generated and parallelized on activation, irrespective of the settings. More information: Runtime Parameters of DataStore Objects.

Clustering in active data tables (A tables)

Clustering at database level makes it possible to access DataStore object much more quickly. As a clustering criterion, choose the characteristic by which you want to access the data. More information: Multidimensional Clustering.

Indexing

For queries based on DataStore objects, use selection criteria. If key fields are specified, the existing primary index is used. The more frequently accessed characteristic should appear on the left.

If you have not specified the key fields completely in the selection criteria (you can check this in the SQL trace), you can improve the runtime of the query by creating additional indexes. You create these secondary indexes in DataStore object maintenance.

However, you should note that load performance is also affected if you have too many secondary indexes.

Relative Activation Times for Standard DataStore Objects

The following table shows the time saved in runtime activation. The saving always refers to a standard DataStore object that the SIDs were generated for during activation.

Flag		Saving in Runtime
Generation of SIDs During Activation Unique Data Records	x x	approx. 25%
Generation of SIDs During Activation Unique Data Records		approx. 35%
Generation of SIDs During Activation Unique Data Records	x	approx. 45%

The saving in runtime is influenced primarily by the SID determination. Other factors that have a favorable influence on the runtime are a low number of characteristics and a low number of disjointed characteristic attributes. The specified percentages are based on experience, and can differ depending on the system configuration.

 

If you use the DataStore object as the consolidation level, we recommend that you use the write-optimized DataStore object. This makes it possible to provide data in the Data Warehouse layer 2 to 2.5 times faster than with a standard DataStore object with unique data records and without SID generation. More information: Scenarios for Using Write-Optimized DataStore Objects.