STAD getting into sql stmt or part of abap execution taking the longest time

[steven_foo]

Hi All,

In STAD, we could get the information like Sequential Read the Database rows database request. Example below.

Analysis of ABAP/4 database requests (only explicitly by application)
    ---------------------------------------------------------------------------------
    | Connection                    DEFAULT         Request time       849,217 ms   |
    | Database requests total    11,342,767         Commit time              0 ms   |
    | DB Proc. Calls                      0         DB Proc. Time            0 ms   |
    ---------------------------------------------------------------------------------
    | Type of         |Database |        |Requests  |Database | Request |Avg.time / |
    | ABAP request    |    rows |Requests|to buffer |   calls |time (ms)| row (ms)  |
    ---------------------------------------------------------------------------------
    | Total           |8331,640 |  *42767| 6815,518 |1110,744 | 849,217 |     0.1   |
    |                 |         |        |          |         |         |           |
    | Direct read     | 280,030 |  *95785| 6116,255 |         |  94,126 |     0.3   |
    | Sequential read |8051,609 |  *46981|  699,263 |1110,743 | 755,090 |     0.1   |
    | Update          |       1 |      1 |          |       1 |       1 |     1.0   |
    | Delete          |       0 |      0 |          |       0 |       0 |     0.0   |
    | Insert          |       0 |      0 |          |       0 |       0 |     0.0   |
    ---------------------------------------------------------------------------------

1) How do I get the information to the part of which sql is causing the the most sequential read here?

2) At which part of the ABAP program which runs at the internal table process the longest time?

Or where could I find the cause of the ABAP slow running part of the program?

Thanks

[xymanuel · Accepted solution]

Hi Steven,

1.

go to ST03N -> Collector and Performance Database -> Statistical Records & File -> online parameters ->  dialog step statistics

Now in the right panel in the colum "stat/tabrec"  the fields are empty.

Put in the value "5" (application server dependend). This means, the appserver records the used tables to a querydepth of 5 tables.

(should be enough).

After this, you will be able to see, which tables are used in "stad".

Example with a slow access:

This option has a little peformanceimpact, please switch it off after you found which table

is responsible for your performacneimpact.

After identifing the table, i recommend to go to "DBACOCKPIT" and use perormance -> SQL Statements, filter for the table, and analyse the SQL Statement.

2.

For analyses of slow internal tables use either transation SAT (old SE30),

or in an Q System, attach yourself through SM66 to a long running dialog/background with Debug (double click on running process in column "report" -> "debug".

It stops the process in the debugger, and you will have enough time to analyse the internal tables.

To attach online to an running WP, you need debug with replace, which is law critical in productive systems. (S_DEVELOP with DEBUG and ACTVT 02).

Kind Regards Manuel