13.01.2013 Views

OpenEdge Data Management: DataServer for Microsoft SQL Server

OpenEdge Data Management: DataServer for Microsoft SQL Server

OpenEdge Data Management: DataServer for Microsoft SQL Server

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 4: Additional Features to Enhance <strong>Data</strong><strong>Server</strong> Per<strong>for</strong>mance<br />

Monitoring connections with qt_debug<br />

The <strong>Data</strong><strong>Server</strong> log contains messages indicating the status of connections. At startup,<br />

the number of managed connections initialized is written to the log file. If connections<br />

are rejected, this is also logged. If a connection from the ODBC connection pool cannot<br />

be reused, the ODBC driver issues the message DEAD Connection which is written<br />

to the log file.<br />

At the end of a session, the <strong>Data</strong><strong>Server</strong> writes summary in<strong>for</strong>mation about cursor use.<br />

The summary contains the following in<strong>for</strong>mation:<br />

• Needed connections — The number of connections actually used during a<br />

session<br />

• Peak connections — The maximum number of connections used simultaneously<br />

during a session<br />

When debug logging is enabled with the “-Dsrv qt_debug,cursor” switch, a summary<br />

of connection activity is written to the log file. This summary contains:<br />

• Number of connections (defaults to 5)<br />

• Number of peak connections (defaults to 5)<br />

• Highest connection value<br />

• Lowest connection value<br />

• Number of connections pulled out of pool<br />

• Number of connections placed in the pool<br />

• Total sum of active connections<br />

The following excerpt from a dataserv.lg file shows the summary of the managed<br />

connection activity written when the “-Dsrv qt_debug,cursor” switch is used, plus<br />

the standard messages:<br />

16:32:09 : Standard secondary connection:<br />

16:32:09 : Connection chain 0xbc6e64: num_conns 1<br />

16:32:09 : Connection chain 0xbc6e64: peak_conns 1<br />

16:32:09 : Connection chain 0xbc6e64: high_conns 1<br />

16:32:09 : Connection chain 0xbc6e64: low_conns 0<br />

16:32:09 : Connection chain 0xbc6e64: num_off_conns 1<br />

16:32:09 : Connection chain 0xbc6e64: num_on_conns 1<br />

16:32:09 : Connection chain 0xbc6e64: sum_active 1<br />

16:32:09 : Connection chain 0xbc6e64: Needed Connections: 1, (Needed 4 less<br />

than requested)<br />

16:32:09 : Connection chain 0xbc6e64: Peak Connections: 1, (Peaked at 4 less<br />

than requested)<br />

16:32:09 : Connect: 0x1012398 Stmt: 0x1b95f80 Handle: 0x1011d98 Crc:<br />

1613 Proprty: Statement dropped<br />

16:32:09 : Statement cache (-Dsrv PRGRS_PREPCACHE setting) reuse ratio is 0.<br />

For more in<strong>for</strong>mation on using the qt_debug option to the -Dsrv switch, see<br />

Appendix B, “<strong>Server</strong> Related Command Line Utilities and Startup Parameters.”<br />

166 <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>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!