OpenEdge Data Management: DataServer for Microsoft SQL Server
OpenEdge Data Management: DataServer for Microsoft SQL Server
OpenEdge Data Management: DataServer for Microsoft SQL Server
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Appendix D: Using qt_debug to Analyze Per<strong>for</strong>mance<br />
Using qt_debug to analyze per<strong>for</strong>mance<br />
The qt_debug option of the <strong>Data</strong><strong>Server</strong> (-Dsrv) startup parameter (and the<br />
QUERY–TUNING DEBUG phrase) instructs the <strong>Data</strong><strong>Server</strong> to print in<strong>for</strong>mation on the<br />
queries it generates to the dataserv.lg log file. The qt_debug option provides<br />
extended diagnostic capabilities that you can use to determine which parts of your<br />
application might be causing additional network traffic or extra processing by the MS<br />
<strong>SQL</strong> <strong>Server</strong> database. Table 59 lists the diagnostic capabilities of qt_debug.<br />
Table 59: 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><br />
executes.<br />
qt_debug,EXTENDED Prints the <strong>SQL</strong> statements that the <strong>Data</strong><strong>Server</strong><br />
executes plus additional in<strong>for</strong>mation such as cursor<br />
statistics.<br />
qt_debug,CURSOR Prints in<strong>for</strong>mation about the cursors that the<br />
<strong>Data</strong><strong>Server</strong> uses <strong>for</strong> internal calls and <strong>for</strong> opening<br />
queries. It tracks when cursors open and close and<br />
when the <strong>Data</strong><strong>Server</strong> reuses them. It also<br />
summarizes each cursor’s activity. These<br />
diagnostics are especially helpful when determining<br />
<strong>OpenEdge</strong> maximum cursor settings or cursor<br />
“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<br />
<strong>for</strong> some plat<strong>for</strong>ms. Note that any time differences<br />
between what the <strong>Data</strong><strong>Server</strong> and data source<br />
report might be due to network per<strong>for</strong>mance issues<br />
rather than to <strong>Data</strong><strong>Server</strong> 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<br />
<strong>OpenEdge</strong> data (.d) file. Contact Progress Software<br />
Corporation <strong>for</strong> assistance with this file.<br />
Note: This option is not available as a<br />
QUERY–TUNING 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<br />
sure to clear your log file be<strong>for</strong>e using this option to<br />
test a procedure.<br />
Note: Turning on debugging options decreases <strong>Data</strong><strong>Server</strong> per<strong>for</strong>mance. Be sure to<br />
turn off debugging options when you run <strong>Data</strong><strong>Server</strong> applications in production<br />
mode.<br />
358 <strong>OpenEdge</strong> <strong>Data</strong> <strong>Management</strong>: <strong>Data</strong><strong>Server</strong> <strong>for</strong> <strong>Microsoft</strong> <strong>SQL</strong> <strong>Server</strong>
Change language