About Native and Parallel (Bulk) Caching
Native cache loading is designed to enhance caching performance loading the cache. The Enable Cache Loading and Enable Parallel Loading Studio configuration parameter controls whether native caching is enabled or disabled. By default, the native cache loading is enabled.
When a single-source, pass-through view is cached, native cache loading might be supported.
There are several ways to tune the performance associated with data caching. If you have set up caching performance configurations for native and parallel caching options, TDV determines which option is ideal.
If native and parallel caching options cannot be used to move the data, TDV attempts to use JDBC to do the cache loading.
The following cache loading options are supported by TDV:
| • | INSERT/SELECT statements |
| • | Bulk load with the LOAD utility |
| • | Bulk load with bcp, utility (bcp.exe) |
| • | Bulk load with external tables |
| • | Bulk load through database links |
| • | Bulk load using the Bulk Load utility |
| • | Parallel cache load |
When the native caching option can be performed within the same data source, that is the source of the cache data and the target for the cache data reside in the same database or schema, and the data source supports INSERT/SELECT statement, the cache loading will use INSERT/SELECT statement. With the INSERT/SELECT statement method of native caching, almost all data types are supported.
If the INSERT/SELECT statement cannot be used for native caching, TDV tries to use the mechanism that the target data source supports. These options vary by database type.