DataSourceDisableStaticCursor

Enables a workaround for a performance issue that can be caused by the creation of a static cursor on a huge resultset.

When a static cursor is created, the resultset is entirely cached on disk by the ODBC Client. This means that all of the data of the resultset is transferred from the database to the client before SQLExecute returns. When gigabytes of data are transferred, the performance issue is intrusive.

This very large static cursor may be unexpected, for example, when the creation of a keyset-driven cursor failed, or the result of an application that requests a scrollable cursor when only a forward-only cursor is needed.

DataSourceDisableStaticCursors can be set to disable the use of static cursors.

True | False

False

Dynamic

The workaround can be set also from the ODBC connection string. For information about using a connection string with the ODBC Client, refer to the OpenAccess SDK Client Reference.