Carrying out database-specific performance checks
In this recipe, we will see a few examples of problems of the SELECT statements that the code inspector may highlight. This may help in improving performance of the program at the development stage. The performance checks are available in both the transactions SCI and SCII. We will emphasize on the selection of the database-specific performance checks during variant creation, and some of the typical statements/constructs that may be caught using code inspector.
How to do it...
Within the checks, expand the Performance Checks category.
From the list of checks that appear, select the checks shown in the following screenshot:
How it works...
The inspection checks the various program and highlights as warning statements that are performance statements. During this, the code inspector checks the syntax of the program and refers to the attributes and technical settings of the tables involved.
CHECKorEXITstatements used within aSELECTstatement instead...
