OpenEdge Data Management: DataServer for Microsoft SQL Server
OpenEdge Data Management: DataServer for Microsoft SQL Server
OpenEdge Data Management: DataServer for Microsoft SQL Server
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Using qt_debug to Analyze Per<strong>for</strong>mance<br />
Using qt_debug to analyze per<strong>for</strong>mance<br />
D–2<br />
The qt_debug option of the <strong>Data</strong><strong>Server</strong> (-Dsrv) startup parameter (and the QUERY–TUNING DEBUG<br />
phrase) instructs the <strong>Data</strong><strong>Server</strong> to print in<strong>for</strong>mation on the queries it generates to the<br />
dataserv.lg log file. The qt_debug option provides extended diagnostic capabilities that you<br />
can use to determine which parts of your application might be causing additional network traffic<br />
or extra processing by the MS <strong>SQL</strong> <strong>Server</strong> database. Table D–1 lists the diagnostic capabilities<br />
of qt_debug.<br />
Table D–1: Diagnostic options<br />
Option Description<br />
qt_no_debug Supplies no debug in<strong>for</strong>mation. This is the default.<br />
qt_debug,<strong>SQL</strong> Prints the <strong>SQL</strong> statements that the <strong>Data</strong><strong>Server</strong> executes.<br />
qt_debug,EXTENDED Prints the <strong>SQL</strong> statements that the <strong>Data</strong><strong>Server</strong> executes<br />
plus additional in<strong>for</strong>mation such as cursor statistics.<br />
qt_debug,CURSOR Prints in<strong>for</strong>mation about the cursors that the <strong>Data</strong><strong>Server</strong><br />
uses <strong>for</strong> internal calls and <strong>for</strong> opening queries. It tracks<br />
when cursors open and close and when the <strong>Data</strong><strong>Server</strong><br />
reuses them. It also summarizes each cursor’s activity.<br />
These diagnostics are especially helpful when<br />
determining <strong>OpenEdge</strong> maximum cursor settings or<br />
cursor “leaks” that your application might have.<br />
qt_debug,PERFORMANCE Prints in<strong>for</strong>mation on the amount of time that certain<br />
operations take. These statistics are available only <strong>for</strong><br />
some plat<strong>for</strong>ms. Note that any time differences between<br />
what the <strong>Data</strong><strong>Server</strong> and data source report might be due<br />
to network per<strong>for</strong>mance issues rather than to <strong>Data</strong><strong>Server</strong><br />
or data source behavior.<br />
qt_debug,CALL_SUMMARY Prints in<strong>for</strong>mation on cursors and timing. This<br />
in<strong>for</strong>mation is supplied in summary <strong>for</strong>m as an <strong>OpenEdge</strong><br />
data (.d) file. Contact Progress Software Corporation <strong>for</strong><br />
assistance with this file.<br />
Note: This option is not available as a QUERY–TUNING<br />
phrase option.<br />
qt_debug,VERBOSE Prints all of the in<strong>for</strong>mation gathered by the other<br />
qt_debug options.<br />
Note: This option generates a very large log file. Be sure<br />
to clear your log file be<strong>for</strong>e using this option to test a<br />
procedure.<br />
Note: Turning on debugging options decreases <strong>Data</strong><strong>Server</strong> per<strong>for</strong>mance. Be sure to turn off<br />
debugging options when you run <strong>Data</strong><strong>Server</strong> applications in production mode.<br />
This connection statement causes the <strong>Data</strong><strong>Server</strong> to report on the time that ODBC operations<br />
take to run:<br />
CONNECT msscdb -Dsrv qt_cache_size,32000,qt_debug,PERFORMANCE.
Change language