Hierarchy
SAP_BW (Software Component) SAP Business Warehouse⤷
BW-BEX-OT (Application Component) OLAP Technology⤷
RSDDTREX (Package) TREX Aggregate
Basic Data
| Data Element | RSDDTREXBLOCKSIZE |
| Short Description | Block Size while filling a BWA index |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | RSDDTREXBLOCKSIZE | |
| Data Type | INT4 | 4-byte integer, integer number with sign |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 11 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Block Size |
| Medium | 15 | Block Size |
| Long | 29 | Block Size (HPA Index Filling |
| Heading | 29 | Block Size (HPA Index Filling |
Documentation
Definition
The block size determines how large the blocks are that are used to optimize an index during filling on the HPA engine. In order to ensure that the memory consumption on the HPA engine does not get too large during optimization of a new index, the index should be optimized at regular intervals. These intervals can be determined by the blocks.
The blocks are formed by the selection of a field in the table or the index. If there is an irregular or unfavorable distribution of the data, blocks can become significantly larger or smaller as selected in the BLOCKSIZE parameter. If problems arise due to this (memory bottlenecks), change the block size.
The value to be selected depends on the size of your HPA server. It should be between 1,000,000 and 5,000,000.
Use
Dependencies
Example
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 700 |
