Progress Sonic ESB Configuration and Management Guide

Chapter 6: Driver Connection Properties and Data Types by Database Brand
Table 17. Connection Properties for the Microsoft SQL Server Driver (continued)
Property Description
SelectMethod
OPTIONAL
{direct | cursor}
A hint to the driver that determines whether the driver requests a database
cursor for Select statements. Performance and behavior of the driver are
affected by this property, which is defined as a hint because the driver
might not always be able to satisfy the requested method.
● Direct — When the driver uses the Direct method, the database
server sends the complete result set in a single response to the driver
when responding to a query. A server-side database cursor is not
created. Typically, responses are not cached by the driver. Using this
method, the driver must process all the response to a query before
another query is submitted. If another query is submitted (using a
different statement on the same connection, for example), the driver
caches the response to the first query before submitting the second
query. Typically, the Direct method performs better than the Cursor
method.
● Cursor — When the driver uses the Cursor method, a server-side
cursor is requested. The rows are retrieved from the server in blocks
when returning forward-only result sets. The JDBC Statement
method setFetchSize can be used to control the number of rows that
are retrieved for each request. Performance tests show that the value
of setFetchSize significantly impacts performance when the Cursor
method is used. There is no simple rule for determining the
setFetchSize value that you should use. We recommend that you
experiment with different setFetchSize values to determine which
value gives the best performance for your application. The Cursor
method is useful for queries that produce a large amount of data,
particularly if multiple open result sets are used.
The default is Direct.
197 Progress Sonic ESB Configuration and Management Guide 8.5