Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SAP Sybase SQL Anywhere 16.0 » SQL Anywhere Server - SQL Usage » Performance improvements, diagnostics, and monitoring » Performance monitoring and diagnostic tools » Diagnostic tracing


Performing request trace analysis

When you have a specific application or request that is problematic, you can perform a request trace analysis to determine the problem. Request trace analysis configures the Database Tracing Wizard to narrow diagnostic data gathering to only the user, connection, or request that is experiencing the problem.


To start a tracing session, TCP/IP must be running on the database server(s) on which the tracing database and production database are running.

You must have the DIAGNOSTICS system role, and the MANAGE PROFILING, SERVER OPERATOR, and SELECT ANY TABLE system privileges.

Context and remarks

Using the various data viewing tools in Application Profiling mode, you can identify any potential conflicts or bottlenecks.

  1. In Sybase Central, use the SQL Anywhere 16 plug-in to connect to the database.

  2. Click Mode » Application Profiling.

    If the Application Profiling Wizard appears, click Cancel.

  3. Right-click the database and click Tracing or click Tracing » Configure And Start Tracing.

  4. Follow the instructions in the Database Tracing Wizard.

  5. When you are done gathering tracing data, right-click the database and click Tracing » Stop Tracing With Save.

  6. In the Application Profiling Details pane, click Open An Analysis File Or Connect To A Tracing Database.

  7. Click In A Tracing Database, and click Open.

  8. Complete the User Name and Password fields and click OK.

  9. In the Application Profiling Details pane, click the last entry in the Logging Session ID list.

  10. Click Database Tracing Data tab at the bottom of the Application Profiling Details pane.


You can select from several tabs that provide you with different views of the data gathered for your analysis. For example, the Summary tab allows you to see all requests executed against the database during the tracing session, including how many times each request was executed, execution duration times, the user who executed the request, and so on. If the list is long and you are looking for a specific request, click the Filtering title bar on the Summary tab and enter a string in the SQL Statements Containing field.


To view more details about a specific request, right-click the request and click Show The Detailed SQL Statements For The Selected Summary Statement. The Details tab opens. Right-click the row containing the request, and additional choices for information are provided, including viewing additional SQL statement, connection, and blocking details.