cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Performance Problem SQL on RESB

Private_Member_19084
Active Contributor
0 Likes
1,263

Hi experts,

since a few days we have a big performance impact by sql-statements on tabel RESB.

e.g. we have select-statements, which did take around 10 minutes and now over 3 hours.

We have already checked indizes and table consistent. Also table checks in DB02.

If I make the same sql on our testing system it is still fast, so only in the productive sytem we are facing this problem.

The table size in both systems is similar.

At the moment selecting around 1000 rows in PROD systems takes more than 10 minutes.

In Q System it takes just a few minutes for more than 100 000.

Can someone help to analyze the problem?

Thank you

View Entire Topic
0 Likes

Hi Cristian.

You can check the SQL Statments with high cost to the system.

Check this in ST04 or dbacockpit, > Performance > SQL Statment Analysis > Shared Cursor Cache.

On right hand screen you can filter the SQL Statments and show the cost through EXPLAIN buton and check the Source Code in 'ABAP Source" Buton.

In this point you have conditions to analyse whether you need to create a new Index or send the Program Code to be revised by Abap team.

Check the table statistics in DB20 tcode.

regards,

Mauricio Montoya