Use the application profiling feature to determine whether performance problems are caused by:
long application processing times
poor query plans
contention for shared hardware resources such as CPU or disk I/O
contention for database objects
suboptimal database design
When troubleshooting poor database performance, the first task is to determine whether the application or the database server is the primary cause. To determine how much processing time a client application is consuming, use the Details tab in the application profiling tool and filter the results by a single connection. If there are time differences between different requests from that connection, then the primary delay is within the application client.
If the database server is affecting performance, you will need to identify the specific cause.
Application Profiling does not capture an event, but captures long-running statements within the event. To capture an event, embed the event code within a procedure and call the procedure from the event. Before running the procedure, turn on tracing with a custom level that specifies low detail with no conditions on statement capture. When the tracing session is finished, turn off Application Profiling.
See also |
Discuter à propos de cette page dans DocCommentXchange.
|
Copyright © 2013, SAP AG ou société affiliée SAP - SAP Sybase SQL Anywhere 16.0 |