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.

Large rows—the PRGRS_MINBUF option<br />

ODBC options<br />

Some data rows can be very large; <strong>for</strong> example, in a MS <strong>SQL</strong> <strong>Server</strong> database, rows<br />

often have large fields such as IMAGE and MEMO. The ODBC protocol specifies a<br />

dynamic buffer allocation process <strong>for</strong> handling large rows that do not initially fit into<br />

clients’ buffers; however, some drivers do not yet follow the correct ODBC protocol and<br />

do not handle these large rows correctly. Use the -Dsrv PRGRS_MINBUF,size option to<br />

<strong>for</strong>ce a minimum buffer size. For example, -Dsrv PRGRS_MINBUF,15000 enables the<br />

<strong>Data</strong><strong>Server</strong> to handle 15K rows even with drivers that fail to follow the ODBC protocol.<br />

The optimal setting <strong>for</strong> PRGRS_MINBUF is the size of the largest record data size plus<br />

500 bytes. This can prevent run-time record expansion during the retrieval of query<br />

results.<br />

Notes: Do not use this option when the -Dsrv BINDING switch is set to 3. With the<br />

binding set to 3, the size of the data is known, and this switch will cause the<br />

allocation of unneeded additional memory.<br />

It is often difficult to determine when there is a buffer size problem and how to<br />

choose the correct value <strong>for</strong> PRGRS_MINBUF. Be careful when using this option.<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> 327

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

Saved successfully!

Ooh no, something went wrong!