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.

ODBC options<br />

Table 56: <strong>Data</strong><strong>Server</strong> options (2 of 3)<br />

Option Description<br />

LOGGINGLEVEL Specifies the level at which log entries<br />

are written. For more in<strong>for</strong>mation, see<br />

the “Analyzing application execution<br />

with Enhanced Logger” section on<br />

page 230.<br />

LOGENTRYTYPES Specifies one or more types of log<br />

entries. For more in<strong>for</strong>mation, see the<br />

“Analyzing application execution with<br />

Enhanced Logger” section on page 230.<br />

PRGRS_MAX_BLOCKSIZE Specifies the size in bytes of the total<br />

allowable memory <strong>for</strong> all block cursors.<br />

By default, this value is set to<br />

ODBC_DEF_MAXBLOCKSZ, or 1MB.<br />

PRGRS_MINBUF Specifies the minimum size of the buffer<br />

used to get data from the <strong>Data</strong><strong>Server</strong>.<br />

Use this keyword only with drivers that<br />

fail to fetch large records. The default<br />

value is 500 bytes. If you specify a value<br />

smaller than the default, <strong>OpenEdge</strong><br />

uses the default value.<br />

The optimal setting <strong>for</strong> PRGRS_MINBUF is<br />

the size of the largest record data size<br />

plus 500 bytes. This can prevent<br />

run-time record expansion during the<br />

retrieval of query results.<br />

Note: Do not use this option when the<br />

-Dsrv BINDING switch is set to 3. With<br />

the binding set to 3, the size of the data<br />

is known, and this switch will cause the<br />

allocation of unneeded additional<br />

memory.<br />

PRGRS_NATIVE_LOCKWAIT Specifies the server-based wait period in<br />

which the server will block wait <strong>for</strong><br />

access to a locked resource be<strong>for</strong>e<br />

returning to a MSS <strong>Data</strong><strong>Server</strong> client<br />

application. The default value is zero,<br />

meaning that control is returned to the<br />

client immediately upon receiving a lock<br />

condition from the server.<br />

Note: A number of milliseconds is<br />

recommended at startup <strong>for</strong><br />

transactional applications that anticipate<br />

a higher contention <strong>for</strong> server resources.<br />

The optimal value is application-specific.<br />

PRGRS_NO_INDEX Suppresses index creation at schema<br />

import time. If you specify a value of 1 <strong>for</strong><br />

-Dsrv PRGRS_NO_INDEX, you must<br />

create the indexes manually in the<br />

schema holder.<br />

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

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

Saved successfully!

Ooh no, something went wrong!