Analyzing Results in the Worklist

Prerequisites

To analyze results in the SQL Performance Tuning Worklist tool, you need the authorization profile for data read access.

See also: Tool Availability and Technical Requirements

Context

Target Audience

  • ABAP developers
  • AS ABAP system administrators

Procedure

  1. To access the data selection screen of the Worklist tool, launch transaction SWLT.
  2. In the selection screen of the SQL Performance Tuning Worklist, specify the object dataset and the data sources , or select a variant (if available) that already comprises all relevant settings.
  3. Press F8 or choose the Execute icon in the toolbar.

Results

Based on your selection options, the SQL Performance Tuning Worklist generates a list of findings that are displayed in a compressed overview. Starting from this Result Overview display, you can double-click the line in question and request the details views for runtime data or results from the respective static checks, or for both, depending on your choice of data sources.
Displaying Results in the SQL Performance Tuning Worklist

Case A: SQL Monitor Data Is Merged with Corresponding Results from Static Checks

Result Overview

In this view, the runtime data from the SQL Monitor is merged with results of static checks from the Code Inspector or ABAP Test Cockpit by source code position - if you have selected both data source options before.

When standard settings are used, the results are sorted according to the number of executions or the execution time so that you are able to identify the performance hotspots - just from here.

The left columns represent the most important runtime data indicators:
  • Total number of executions of an SQL statement (DB Executions)
  • Total consumption time measured for an SQL statement (Total DB Time)
  • Mean consumption time per execution (DB Mean Time)
Result Overview with most Important Runtime Data
The light blue columns represent the most important static check fields, such as the
  • Number of findings for one SQL statement
  • Check Title
  • Check Message.

In the Result Overview also the values for the Priority, Severity and the Effort estimation are displayed. This data has been computed by Code Inspector (or ATC) based on specific calculation rules.

Result Overview with most Important Static Check Data

The light orange columns provide additional metadata information about the involved database table, such as the buffering type, the total number of columns, the number of key columns, the width, the size, and the type of table.

Result Overview with Additional Information on the Involved Database Tables

Detailed View with Runtime Data from SQL Monitor

Starting from the Result Overview, you can double-click the line in question and request the detail view for runtime data of the corresponding SQL statement. From the detailed view that is now populated with runtime data from SQL Monitor results, you can perform advanced analysis steps. In particular, you can determine the entry point of the processes or database operations, or navigate to the source code position.

Detailed View on Runtime Data from SQL Monitor

Detailed View with Results from Static Code Scans

By double-clicking a line in the Result Overview, you get a detail view with results from static code scans of the corresponding SQL statement. Using this view , you can analyze the findings from the static checks with regard to their relevance for possible code optimization. Here, the values on priority, severity, and estimated work effort are of particular relevance.

Detailed View on Results from Static Code Scans
In addition, you can access …
  • Documentation of the specific check by clicking the corresponding button in the toolbar.
  • Additional Information that provides you with stack information (if available), which you can use to decide whether the calling or the called program unit has to be changed. If no stack information is available, the link refers to the relevant source code position instead.
Accessing Additional Information (LOOP location) for a Static Code Check

Case B: Results from Code Coverage Are Used in Place of SQL Monitor Data

Using results from Coverage Analyzer or Usage Procedure Logging provides you at least with the number of executions at the level of processing blocks, such as ABAP procedures (methods, function modules) or program events (field Processing Block Executions). In particular, it enables you to find ABAP code areas that are executed very often or, conversely, are never used in your processes.

If you double-click a line in the Result Overview, you get a detail view with results from static code scans of the corresponding processing block or statement.

The Result View Displays a Counter That Indicates the Number of Executions of a Processing Block or Statement