OpenEdge Data Management: DataServer for Microsoft SQL Server

Troubleshooting
8–10
Wait time for asynchronous connections—the PRGRS_WAIT_DELAY option
The PRGRS_WAIT_DELAY switch allows you to determine the number of seconds you will allow
the DataServer to delay further execution while waiting for the ODBC driver to respond to a
request that may initiate a lock on a database resource. The delay is initiated when the NO-WAIT
option is used in your ABL and the DataServer is awaiting a response to a database request made
through the ODBC driver to MS SQL Server. The PRGRS_WAIT_DELAY switch is ignored unless
you are running in ODBC asynchronous mode. Check your driver and OpenEdge connection
requirements to determine if you are allowed to run in asynchronous mode.
Preserve cursors—the -Dsrv MSS_PRESERVE_CURS,1 option
The -Dsrv MSS_PRESERVE_CURS,1 startup option allows server side cursors in Microsoft SQL
Server to be preserved beyond a transaction boundary. Under many circumstances, preserved
cursors can result in a significant performance improvement. Enabling this feature can result in
enhanced performance, but performance gains are not guaranteed and in limited circumstances
performance degrades. For this reason, this option is disabled by default. To test if preserve
cursors benefit your application, enable this option by toggling the switch on with -Dsrv
MSS_PRESERVE_CURS,1.
RECID Buffer size—the ZPRGRS_RECID_BUF_SIZE,nnn Option
The DataServer for MS SQL Server tries to select a unique index over each table defined in your
schema holder to support the Progress RECID/ROWID functions. RECID functionality enables
backward and forward scrolling in the DataServer product. The RECID buffer is used to sort key
information about the unique index selected to support RECID. The default RECID buffer size is
245 bytes. The space is used dynamically to allocate the RECID buffer for a given record. The
RECID buffer size needs to be large enough to contain all the key information regarding the
unique index. If the unique index selected is a composite of many columns or contains large
column names, the RECID key information might exceed the RECID buffer size and issue error
message 2090. If you exceed the RECID buffer limit, Progress Software Corporation first
recommends that you try to find an alternative unique index with a smaller number of key fields.
This should help to improve performance during record access as well. You can change the
RECID index in the Data Dictionary by selecting the DataServer button from the Table
Properties of the table in your schema holder.
If it is not possible to change the selected RECID unique index for the table that is causing the
buffer overflow, you can expand the area by setting the startup option as follows:
-Dsrv ZPRGRS_RECID_BUF_SIZE,nnn
Where nnn is the new size of the area in bytes. The range limits for nnn are inclusive of values
between 44 to 1024.
You can expand the RECID buffer size to a maximum of 1000 bytes. The minimum size is 44
bytes. The algorithm to determine minimum adjusted size is as follows:
• 9 + Length of first Index column name + Length of first column data + 17
• + Length of second Index column name + Length of second column data + 22
• + Length of third Index column name + Length of third column data + 22
• + ...