SQL Performance trace

To obtain an overview of the behavior of the R/3 System, you can record various processes during the execution of an individual object. To analyze performance problems with database accesses, activate the SQL trace and the buffer trace from transaction ST05.

The SQL trace records SQL statements. There may be considerable differences between the SQL statement formed on the ABAP level and the SQL statement that is received by the database.

A buffer trace lets you trace SQL statements that access buffered tables. SQL statements that access buffered tables can cause buffer reloads, which are indicated in a buffer trace. An SQL statement accessing a buffered table can result in a completely different SQL statement if it cannot be satisfied by the R/3 table buffer.

Initial Screen:

To access the SQL Performance Trace, use transaction ST05 or from the R/3 initial screen, choose System ® Utilities ® SQL Trace.

Before activating an SQL Performance Trace for a report or a transaction, you should execute the report one time to prevent the buffer load process for the R/3 table buffer, the R/3 program buffer, and so on, from being included in the subsequent trace.

The trace can be activated in the production system without any risk of creating errors or inconsistencies.

The trace can be activated by any user and for any object. When activating the trace, ensure that you are not using multiple user sessions or running other processes such as background jobs or update processes under the same user ID on this application server. These activities would make the SQL Performance Trace difficult to interpret.

For each application server, there is only one active trace file. Therefore, on a given application server, only one user can activate a trace. The default size of the trace file is 800 KB. SAP recommends increasing the size of the trace file to 16 MB by setting the parameter rstr/max_diskspace to 16 384 000.

SQL Trace Overview:

The R/3 database interface receives an SQL statement from the ABAP program and converts it to an SQL statement that can be processed by the database.

For each database operation, the SQL trace measures the time taken from the sending of the request to the database server to the receipt of the results for the request on the application server via the R/3 database interface (including the time spent in the network between the application server and the database server).

The data written to the trace file includes the database response time, a time stamp, the number of transferred data records, the database return code, the text of the SQL statement, and additional administrative information for each database operation.
13

RELATED POST

SAP SCRIPT SAMPLE CODE

CALL FUNCTION PART FOURSAP ABAP

CALL FUNCTION PART FIVESAP ABAP

CALL METHOD SAP ABAP

CALL SCREENSAP ABAP

CALL TRANSACTIONSAP ABAP