Data Load Performance

Contents:
Data load performance considerations.

SAP AG 1999

Data Load Performance: Unit Objectives

At the conclusion of this unit, you will be able to:

Describe the BW performance issues relating to data loads.

List the data load recommendations for achieving better performance.

SAP AG 1999

Buffer Number Range Objects

If a large quantity of transaction data should be uploaded into the BW, the number range buffer should be increased for the dimensions with a high expected number of rows.

Step 1 Get the number range of all involved objects.

SAP AG 1999

Buffer Number Range Objects

SAP AG 1999

Buffer Number Range Objects

Step 2

Change the Buffering of the Number Range Objects

SAP AG 1999

Buffer Number Range Objects

SAP AG 1999

Delete Secondary Indexes Before Loading Data

Issue
Existence of secondary indexes on fact tables slows data load performance drastically.
It requires that inserts are made into indexes as well as fact table - much more work involved. Dropping secondary indexes prior to data load means that inserts are made to fact table only. Indexes can be quickly rebuilt after data load is finished.
SAP AG 1999

Using InfoCube Data Load Performance Tools

Create Index button: set automatic index drop / rebuild

Statistics Structure button: possibility to recalculate DB statistics after a data load

SAP AG 1999

Possible Settings for Indices and DB Statistics

SAP AG 1999

Load Master Data before Transaction Data

Issue
The master data load creates the SIDs to the keyvalues and the navigational attribute values.
This avoids your transaction data from containing many characteristic attributes for which a new SID must be determined. The insert on the characteristic table for loading the transaction data is no longer necessary.

SAP AG 1999

Load Parallel

Issue
When loading large quantities of data it is recommended that you split the data into several files and take advantage of multiple processors to improve performance. These files can then be loaded in parallel into the BW with several requests.
Prerequisites

Multiple processors Quick Raid

SAP AG 1999

Set Package Size

Issue
The size of an IDOC determines the granularity for the database COMMITS and as a result can have an effect on performance.

SAP AG 1999

Additional Data Load Tips

Use a predefined record length (ASCII file) when loading from a file. If possible load the data from a file from the application server and not from the client workstation.

SAP AG 1999

Additional Data Load Tips

Create InfoCube in proper tablespaces (see note 156784). Run loads at off hours. Avoid large loads across a network. Avoid reading load files from tape. (copy to disk first) Avoid placing input load files on the same disk drives or controllers as the tables being loaded.

SAP AG 1999

Data Load Performance: Unit Summary

Now you are able to:

Describe the BW performance issues relating to data loads.

List the data load recommendations for achieving better performance.

SAP AG 1999