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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

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

Table 24: Query-tuning options (3 of 4)<br />

Option Description<br />

NO-QUERY-UNIQUE-ADDED Specifies that <strong>OpenEdge</strong> should omit the record<br />

identifier from the end of the query’s generated<br />

ORDER BY clause when trying to obtain record<br />

uniqueness from a selected non-unique index. A<br />

sort order that is modified to derive uniqueness<br />

may produce a query that can’t find a useful index<br />

to per<strong>for</strong>m sorting thus impacting query<br />

per<strong>for</strong>mance.<br />

Note: If you elect to use this option, the query<br />

may find an index match to provide better<br />

per<strong>for</strong>mance. However, turning off uniqueness in<br />

a query where scrolling is required may result in<br />

behavior that is incompatible with the <strong>OpenEdge</strong><br />

ABL. Only use this option when compatibility is<br />

not required and can be overlooked <strong>for</strong> the sake<br />

of better per<strong>for</strong>mance.<br />

FIREHOSE-CURSOR Specifies at the query level that the firehose<br />

cursor type should be considered to satisfy the<br />

query when the NO-LOCK phrase is used.<br />

Note: This query-level option overrides the<br />

connection-level -Dsrv options, QT_FIREHOSE<br />

and QT_NO_FIREHOSE that determine if firehose<br />

cursors should be considered <strong>for</strong> the <strong>Data</strong><strong>Server</strong><br />

connection.<br />

NO-FIREHOSE-CURSOR Specifies at the query level that the firehose<br />

cursor type should not be considered to satisfy<br />

the query when the NO-LOCK phrase is used.<br />

Notes:This query-level option overrides the<br />

connection-level -Dsrv options, QT_FIREHOSE<br />

and QT-NO-FIREHOSE that determine if firehose<br />

cursors should be considered <strong>for</strong> the <strong>Data</strong><strong>Server</strong><br />

connection.<br />

By default, firehose cursors are available to<br />

satisfy NO-LOCK queries during a <strong>Data</strong><strong>Server</strong><br />

session. It is generally recommended this default<br />

use be retained and overridden by<br />

QT-NO-FIREHOSE on an individual query basis in<br />

the event that slow query per<strong>for</strong>mance is<br />

observed on a very large result set.<br />

172 <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!