Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

performance affect due to sequential access

Former Member
0 Kudos

Hi,

We are facing a performance problem in our system. we are running program with select statement with proper indexing followed but still it is showing as a sequential read in SM50. This is happening for SAP std programs also.

Database statistics are also updated last week.Why still it is showing as a sequential read. Most of the large tables shows sequential read only. whether it can relate to memory or any other issues.

Regards,

Karthik.k

2 REPLIES 2

christian_wohlfahrt
Active Contributor
0 Kudos

HI Karthik!

SM50 is not a proper tool for analyzing select statements. Either only primary key, maybe also an access with unique secondary index will be displayed as direct access, the rest is counted as sequential - even if good secondary indices are used.

Make a SQL-trace (ST05) to check the access. Here you can see, which index (sometimes even with no. of index fields) is used. If this looks OK, don't worry about SM50. If you have bad accesses, check the source code and the actual filling of the select fields - even if all fields are programmed, not all are filled in a program all the time.

Regards,

Christian

0 Kudos

Use ST05 for SQL performance trace.