Hi All,
I am new to this ABAP field..
I know how to do SQL trace ....But what I am not getting is " <b>HOW CAN WE TELL FROM THE OUTPUT OF SQL TRACE, THAT THIS IS THE CAUSE OF SLOW PERFORMANCE OF A REPORT</b>" Based on what are we determining the performance?
Can Anybody help me here pls?............
Kelly
Hi Kelly,
if you really have no idea, why a report is slow, then you have to start with SE30 (runtime analysis).
There are three bargraphs: ABAP / database / system.
System should be more or less nothing.
If ABAP is bigger than database: have a look at slow abap-statements (normally operations with internal tables: read, delete, loop where,...); classic reason: to much reads without binary search / sorted table / hashed table use.
If database is bigger than ABAP: have a look at your SQL statements. If you can see already forgotten key fields, fine - otherwise SQL trace will bring help in analyzing.
A SQL trace itself says nothing about overall performance (which is done by runtime analysis), only about database part. But 'normally' programmers have their ABAP-part in control and struggle only with slow selects: that's the reason, why often SQL trace is used immediately.
I hope, this brings a little bit light in your question,
regards,
Christian
Hi Kelly
Try <b>"Runtime Analysis Tool"</b> instead. The transaction code is <b>"SE30"</b>. There you can analyse database calls, etc... and see what takes how much time during runtime.
*--Serdar
From the SQL trace you can find,
1. are there recurrsive database calls
2. What index a particular selecte statement is using
3. What is the cost per database read
4. Which database read is taking more time, etc
Regards
Raja
Add a comment