topic Re: Performance Tunning in Application Development and Automation Discussions

Performance Tunning

Former Member — Thu, 15 Mar 2007 13:32:23 GMT

Can anybody help in writting the steps to be followed in SQL Trace as per performance tunning is concerned ?

How to effictively use the SE30 transaction & what are the things we should look for after performing this transaction for a particular program ?

Re: Performance Tunning

Former Member — Thu, 15 Mar 2007 13:37:19 GMT

Hi,

1) Dont use nested seelct statement

2) If possible use for all entries in addition

3) In the where addition make sure you give all the primary key

4) Use Index for the selection criteria.

5) You can also use inner joins

6) You can try to put the data from the first select statement into an Itab and then in order to select the data from the second table use for all entries in.

7) Use the runtime analysis SE30 and SQL Trace (ST05) to identify the performance and also to identify where the load is heavy, so that you can change the code accordingly

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5d0db4c9-0e01-0010-b68f-9b1408d5f234

1. Use Inner Joins

2. INTO TABLE

3. No nested loop

4. FOR ALL ENTRIES

5. Use as much of the key as possible

5. try to use primary or secondary keys in where condition. When using key fields, start with first key field.

6. Select only the fields you need for display/processing - avoid select *

reward if useful

Regards,

Anji