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.

ODBC options<br />

Wait time <strong>for</strong> asynchronous connections—the PRGRS_WAIT_DELAY option<br />

The PRGRS_WAIT_DELAY switch allows you to determine the number of seconds you will<br />

allow the <strong>Data</strong><strong>Server</strong> to delay further execution while waiting <strong>for</strong> the ODBC driver to<br />

respond to a request that may initiate a lock on a database resource. The delay is<br />

initiated when the NO-WAIT option is used in your ABL and the <strong>Data</strong><strong>Server</strong> is awaiting<br />

a response to a database request made through the ODBC driver to MS <strong>SQL</strong> <strong>Server</strong>.<br />

The PRGRS_WAIT_DELAY switch is ignored unless you are running in ODBC<br />

asynchronous mode. Check your driver and <strong>OpenEdge</strong> connection requirements to<br />

determine if you are allowed to run in asynchronous mode.<br />

Preserve cursors—the -Dsrv MSS_PRESERVE_CURS,1 option<br />

The -Dsrv MSS_PRESERVE_CURS,1 startup option allows server side cursors in<br />

<strong>Microsoft</strong> <strong>SQL</strong> <strong>Server</strong> to be preserved beyond a transaction boundary. Under many<br />

circumstances, preserved cursors can result in a significant per<strong>for</strong>mance improvement.<br />

Enabling this feature can result in enhanced per<strong>for</strong>mance, but per<strong>for</strong>mance gains are<br />

not guaranteed and in limited circumstances per<strong>for</strong>mance degrades. For this reason,<br />

this option is disabled by default. To test if preserve cursors benefit your application,<br />

enable this option by toggling the switch on with -Dsrv MSS_PRESERVE_CURS,1.<br />

RECID Buffer size—the ZPRGRS_RECID_BUF_SIZE,nnn Option<br />

The <strong>Data</strong><strong>Server</strong> <strong>for</strong> MS <strong>SQL</strong> <strong>Server</strong> tries to select a unique index over each table<br />

defined in your schema holder to support the Progress RECID/ROWID functions. RECID<br />

functionality enables backward and <strong>for</strong>ward scrolling in the <strong>Data</strong><strong>Server</strong> product. The<br />

RECID buffer is used to sort key in<strong>for</strong>mation about the unique index selected to support<br />

RECID. The default RECID buffer size is 245 bytes. The space is used dynamically to<br />

allocate the RECID buffer <strong>for</strong> a given record. The RECID buffer size needs to be large<br />

enough to contain all the key in<strong>for</strong>mation regarding the unique index. If the unique<br />

index selected is a composite of many columns or contains large column names, the<br />

RECID key in<strong>for</strong>mation might exceed the RECID buffer size and issue error message<br />

2090. If you exceed the RECID buffer limit, Progress Software Corporation first<br />

recommends that you try to find an alternative unique index with a smaller number of<br />

key fields. This should help to improve per<strong>for</strong>mance during record access as well. You<br />

can change the RECID index in the <strong>Data</strong> Dictionary by selecting the <strong>Data</strong><strong>Server</strong> button<br />

from the Table Properties of the table in your schema holder.<br />

If it is not possible to change the selected RECID unique index <strong>for</strong> the table that is<br />

causing the buffer overflow, you can expand the area by setting the startup option as<br />

follows:<br />

-Dsrv ZPRGRS_RECID_BUF_SIZE,nnn<br />

Where nnn is the new size of the area in bytes. The range limits <strong>for</strong> nnn are inclusive<br />

of values between 44 to 1024.<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> 329

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

Saved successfully!

Ooh no, something went wrong!