SM50 screen intrepretation

[Former Member]

Hi Team,

I have a question.

Database                         Number              Time (usec)         Recs.

Direct Read                       157              26,180                  18
Sequential Read                 1,037            178046                   167
Insert                              0                   0                   0
Update                            299           2,391,899                 299
Delete                         29,775           125613597             297,750
Sources                             0  (Bytes)
RSQL                           84,952  (Bytes)
Commit                                          270367963
DB Procedure Calls                  0                   0

Roles / Memory                   Number              Time (usec)

Roll In                             0                   0
Roll Out                            0                   0
Roll                                0  (Bytes)
Page                                0  (Bytes)
Memory (Total)                            100,565,856  (Bytes)
Memory(Total Private)                               0  (Bytes)
Memory (used)                              92,175,776  (Bytes)
Memory (Max. Transaction)                 100,565,856  (Bytes)
Memory (Max. Dialog Step)                 100,565,856  (Bytes)

In this what does recs mean?

Sequential read would mean reading data from the database right ?

Direct read would mean reading from the buffer right?

Can someone please clarify these questions.

Thanks,

[david_liu1 · Accepted solution]

Hello,

You can check the help information via: put the cursor in the field, e.g. "Recs." and then press F1 button, you will get the help information there.

Regards,

David

[Former Member · Accepted solution]

David,

Did you get an F1 help for recs field in SM50. I didnt get it. Thats the reason raised this thread.

[divyanshu_srivastava3 · Accepted solution]

have you checked any system running on NW 7.4

try it there you will get your answer.

[Former Member · Accepted solution]

Havent checked in NW 7.4

[former_member217353]

Dear,

Recs points to number of records effected whether read/write/update/delete

SM50 in Detail: Detailed Information About a Work Process - Monitoring and Administration Tools for ...

Direct read

The term "Direct read" refers to accesses in which a maximum of one line is returned by the database. This includes summarization queries such as SELECT COUNT and fully-qualified primary key accesses.

Sequential Read

A "Sequential Read" refers to all other read database accesses, in which there may be more than one line returned. It is true that the term "Sequential read" is a little deceptive since it implies that blocks are always read sequentially (as in a full table scan). In reality, however, when you perform a trace on these queries you will see that index is used in most cases.

So, "Direct read" and "Sequential read" in SM50 are worthless for a performance analysis. It only shows that the processes are running and processing one of the queries directed at the database interface.

For expensive SQL statements analysis, "Reads/User Calls" value (TCODE BACOCKPIT or ST04OLD) is an indication. If this value is above 15, the SQL statements should be checked in detail.

Regards,

Domnic

[divyanshu_srivastava3]

Hi,

Recs menas "Number of database records affected"

For difference between seq and dir reads refer below.

Regardsm

[Former Member]

Hi,

As,replied by 'David' you can  check the help information via: put the cursor in the field, e.g. "Recs." and then press F1 button.

Here, 'recs' means recreation of existing  reading environment of database either sequential or direct read.

Regards