SAP ABAP Data Element SQLM_D_MAX_RECORDS_EMPTY (Maximum Number of Records (Aggregated by Source Position))
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-DWB-TOO-RTA (Application Component) Runtime Analysis
⤷
SQLM_ADMIN (Package) SQL Monitor: Administration

⤷

⤷

Basic Data
Data Element | SQLM_D_MAX_RECORDS_EMPTY |
Short Description | Maximum Number of Records (Aggregated by Source Position) |
Data Type
Category of Dictionary Type | Direct Type Entry | |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ||
Data Type | CHAR | Character String |
Length | 11 | |
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 | Max. Recs. |
Medium | 15 | Max. Num. Recs. |
Long | 20 | Max. Num. of Recs. |
Heading | 25 | Maximal Number of Records |
Documentation
Definition
This option can be used to limit the amount of used SQLM records, e.g. for performance or simplicity reasons.
By entering a value for this field you define how many source positions (SQL statements) are significant. All SQLM records that belong to these source positions are used.
If cleared or set to zero, this number actually is unlimited.
Use
Dependencies
Example
If you choose the ordering option "By Number of Executions" and enter 10 as "Maximal Number of Records (Aggregated by Source Position)" you will receive all SQLM records (can be more than 10) that are related to the 10 code positions with the highest number of executions.
History
Last changed by/on | SAP | 20141013 |
SAP Release Created in | 740 |