This section describes inserter and reader caching.
When the cache size is greater than 1, the DB Access Module for Sybase uses the Sybase Bulk-Library to perform the insert. The Sybase Bulk-Library has some unique restrictions and features. For example, it expects that all the columns be bound in the same order as in the table schema. Applications must ensure that columns are bound in the correct order.
In addition, applications may be able to take advantage of different kinds of high-speed data transfer by setting some server options, such as Select Into/Bulk Copy, and changing the TDS packet size. In cases where the target table doesn't have an index, bulk insert can result in errors if the server option Select Into/Bulk Copy is not turned on. The Select Into/Bulk Copy option also has an impact on the recoverability of the database, as no data logging is performed. For more details, please see the Sybase documentation on Bulk-Library client programming.
Reader caching is fully supported by the DB Access Module for Sybase. Increasing the cache size, when producing an RWDBReader, increases the number of rows fetched from the server. This reduces the network traffic and increases performance.
Copyright © Rogue Wave Software, Inc. All Rights Reserved.
The Rogue Wave name and logo, and SourcePro, are registered trademarks of Rogue Wave Software. All other trademarks are the property of their respective owners.
Provide feedback to Rogue Wave about its documentation.