How to Identify Expensive SQL Statements?

1. Start ST05.
2. Switch on the SQL trace: “Trace on”.
3. Run the test program (in a different window).
4. Switch off the  SQL trace: “Trace off”.
5. List the SQL statements recorded: “List trace”.

Now, view the SQL trace and check the execution plan.

If you are having performance issues, There are other tools you should also regard when performance problems show up:

• Transaction SE30: The ABAP Profiler
• Transaction DB01: Lockwait Situations
• Transaction ST02: Buffer Statistics
• Transaction ST04: Database Performance Analysis

If you like this post, you may as well like these too:

1. ABAP Open SQL Statements What are some of the OPEN SQL Statements used in ABAP?. Here it is : SELECT OPEN CURSOR, FETCH NEXT, CLOSE CURSOR INSERT UPDATE MODIFY DELETE COMMIT WORK ROLLBACK WORK...
2. ABAP Programs: Using select statements REPORT ZSOURCE1501. * Work areas TABLES: CUSTOMERS, BOOKINGS. * Reading data SELECT * FROM CUSTOMERS. WRITE / CUSTOMERS-NAME. SELECT * FROM BOOKINGS WHERE CUSTOMID = CUSTOMERS-ID AND FLDATE > ’19990501′...
3. ABAP Programs: Working with hide statements REPORT ZSOURCE1704. * work area TABLES CUSTOMERS. * Internal table DATA ALL_CUSTOMERS LIKE CUSTOMERS OCCURS 100 WITH HEADER LINE. * Processing data START-OF-SELECTION. SELECT * FROM CUSTOMERS INTO TABLE ALL_CUSTOMERS....
4. SAP FI FAQs – Financial Statements 1.    Discuss the concept of hierarchy levels with regard to the balance sheet in SAP. There are ten levels possible in the financial statement hierarchy.  For each level, an item...