Académique Documents
Professionnel Documents
Culture Documents
Contents:
Data load performance considerations.
SAP AG 1999
SAP AG 1999
SAP AG 1999
Step 2
SAP AG 1999
SAP AG 1999
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
SAP AG 1999
SAP AG 1999
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
SAP AG 1999
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
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
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
SAP AG 1999