Release 10.1A: OpenEdge Data Management:
DataServer for Microsoft SQL Server

> ## Analyzing performance

> The `qt_debug` option of the DataServer (`-Dsrv`) startup parameter (and the `QUERY–TUNING` `DEBUG` phrase) instructs the DataServer to print information on the queries it generates to the `dataserv.lg` log file. The `qt_debug` option provides extended diagnostic capabilities that you can use to determine which parts of your application might be causing additional network traffic or extra processing by the MS SQL Server database. Table 6–4 lists the diagnostic capabilities of qt_debug.

> Table 6–4: Diagnostic options
> Option | Description
> --- | ---
> `qt_no_debug` | Supplies no debug information. This is the default.
> `qt_debug,SQL` | Prints the SQL statements that the DataServer executes.
> `qt_debug,EXTENDED` | Prints the SQL statements that the DataServer executes plus additional information such as cursor statistics.
> `qt_debug,CURSOR` | Prints information about the cursors that the DataServer uses for internal calls and for opening queries. It tracks when cursors open and close and when the DataServer reuses them. It also summarizes each cursor’s activity. These diagnostics are especially helpful when determining OpenEdge maximum cursor settings or cursor “leaks” that your application might have.
> `qt_debug,PERFORMANCE` | Prints information on the amount of time that certain operations take. These statistics are available only for some platforms. Note that any time differences between what the DataServer and data source report might be due to network performance issues rather than to DataServer or data source behavior.
> `qt_debug,CALL_SUMMARY` | Prints information on cursors and timing. This information is supplied in summary form as an OpenEdge data (`.d`) file. Call Progress Software Corporation Consulting for assistance with this file. Note: This option is not available as a `QUERY–TUNING` phrase option.
> `qt_debug,VERBOSE` | Prints all of the information gathered by the other `qt_debug` options. Note: This option generates a very large log file. Be sure to clear your log file before using this option to test a procedure.

> Note: Turning on debugging options decreases DataServer performance. Be sure to turn off debugging options when you run DataServer applications in production mode.

> This connection statement causes the DataServer to report on the time that ODBC operations take to run:

>     CONNECT msscdb -Dsrv qt_cache_size,32000,qt_debug,PERFORMANCE.

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095