Data access can be tuned and customized by altering a Dynaset's cache and
fetch parameters. Setting FetchLimit to a higher value increases the number of rows
that are fetched with each request, thus reducing the number of network trips
to the Oracle Server, which in turn improves performance.
The cost of increasing the FetchLimit is that it increases memory requirements
on the client-side, and causes more data to be swapped to and from the
temporary cache file on disk. So the proper FetchLimit should be set according to the
client machine configuration and the anticipated size of the query result.
FetchLimit can be set in the following ways:
· By using the CreateCustomDynaset method.
· By modifying parameters of the OO4O entry in the Windows Registry. For Windows
NT and Windows 95, the Registry key is HKEY_LOCAL_MACHINE and the subkey is
software\oracle\oo4o. The OO4O installation creates the following section in the
Registry:
"FetchLimit" = 100
See Also
