The Performance Trace allows to record database access, locking activities, and remote calls of reports and transactions in a trace file and to display the performance log as a list. It also provides extensive support for analyzing individual trace records.
The Performance Trace contains the following tracing features:
* SQL Trace: This allows monitoring of the database access from reports and transactions
* Enqueue Trace: This allows monitoring of the transaction locking system
* RFC Trace: This provides information about Remote Function Calls between instances.
* Buffer Trace : Memory trace
By default, the SQL Trace tool is de-activated, or turned off. Follow the following procedures to get SQL Trace:
1. Start another SAP session
2. Within the new session, enter Transaction Code ST05 ~ the Trace Requests screen is displayed.
3. Return to your original session and prepare to execute your report
4. Return to the Trace Requests screen
5. Select SQL Trace from the Trace Modes area and activate the trace by clicking on the “Trace on” button.You can also use "Activate trace with filter" button.Its better to use trace with filter as you can trace a specified program and work on others at the same time.
6. Return to your original session then execute the report
7. Once the report has successfully executed and returned with data, switch to the other session and click on the “Trace off” button
8. Click on the “List Trace” button to view the results of your SQL Trace for the report
Once you click the “Trace on” button, a Trace File is automatically created.
To compare sequential traces, you must save the Trace File to your system – otherwise it will be overwritten by each new trace you perform.
The top line displays the following information:
* The name of the Transaction (i.e., SESS)
* The Process Identification number ~ PID
* The Process Type (i.e., DIA = Dialog)
* The SAP Client
* The user’s Name
The columns display:
* Duration ~ runtime for the statement in milliseconds & microseconds ~ if you see a listing highlighted, this means this operation exceed the pre-set limit of 10000 milliseconds
* Object ~ for an SQL Trace: Name of the database table
* Op. ~ for an SQL Trace: Name of the operation performed in the database
* Rec ~ for an SQL Trace: Number of records retrieved or processed and passed between the R/3 System and the database
* RC ~ the Return Code of the statement
* Statement ~ an abbreviated listing of the complete statement as logged
#click on the row and then on the explain tab to see the cost of the statement .The estimated cost of the statement should be one for best performance
#If you want to change the select statement and test the cost double click on the column Statement of the row pertaining to the Table in question.Copy the select statement.Open another session of ST05 click on enter SQL statement.Paste the copied code .The variable in the code will be in the place holder format you can put the values instead of place holders too.then click the explain tab it gives the new estimated cost.
阅读(470) | 评论(0) | 转发(0) |
