Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-DWB-TOO (Application Component) Workbench Tools: Editors, Painters, Modelers⤷
SWLT (Package) SQL Performance Tuning Worklist
Basic Data
| Data Element | SWLT_D_EVALUATE_COVERAGE |
| Short Description | Get Processing Block Executions from Coverage Analyzer |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | BOOLE | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| 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 | Exec. Cov. |
| Medium | 20 | Exec. Cov. Analyzer |
| Long | 40 | Get Executions from Coverage Analyzer |
| Heading | 55 | Get Processing Block Executions from Coverage Analyzer |
Documentation
Definition
As a rough alternative to the execution counts provided by the SQL Monitor, you can evaluate those monitored by the Coverage Analyzer. The Coverage Analyzer, if switched on, logs in particular, how often a processing block (a method, function module, subroutine, etc.) has been executed on the servers activated for coverage analysis.
Note that the execution counts of SQL Monitor and Coverage Analyzer in general do not match, because:
- The SQL Monitor counts the execution of a processing block only if an SQL statement is reached during its execution
- The Coverage Analyzer counts every processing block execution
- SQL Monitor and Coverage Analyzer are activated separately, not simultaneously, and not necessarily on the same servers
- SQL Monitor snapshot and coverage results may refer to different systems. This depends on the RFC destination used for creating the snapshot and that specified for the coverage evaluation.
Use
Dependencies
Example
1) If the Coverage Analyzer had already been running for quite a long time before the SQL Monitor was switched on, the execution count of a processing block, according to the SQL Monitor, may be small or even zero, although for the Coverage Analyzer it is much larger.
2) Even if Coverage Analyzer and SQL Monitor have been activated almost simultaneously and on the same servers, the execution count of a processing block can be small or even zero for the SQL Monitor and large for the Coverage Analyzer in case the SQL statement contained in the process block is not reached by every execution of the processing block.
3) If an SQL statement was executed also or only on servers for which the Coverage Analyzer was not switched on, the latter may report less or even zero executions.
History
| Last changed by/on | SAP | 20140117 |
| SAP Release Created in | 740 |
