High Performance Loader Express and Deluxe mode comparison

Problem(Abstract)

This document is a comparison of High Performance Loader's Express and Deluxe Mode Load jobs.

Resolving the problem

High Performance Loader: Mode Comparison for Load Jobs

Express Mode​	Deluxe Mode​
Not logged​	Logged​
Constraints, Indexes, Triggers DISABLED until job completes​	Constraints set to FILTERING WITHOUT ERROR​ Indexes checked​ Triggers evaluated​
Table is exclusively locked for duration of the load​	Table not locked​
Transaction level is a single transaction​	Transaction Level defined by commit interval​
Loaded data not immediately available until table is unlocked and constraints enabled​	Loaded data immediately available​
Limitations: ​ ​ Row size must be less than system page size ​ Blobs not supported ​ Cannot load HDR replicated table ​ Cannot load tables fragmented by rowID ​ Cannot load tables with primary key constraints when child table records reference it​ ​	Limitations: ​ ​ Limited to normal SQL statement limitations. A deluxe load simulates an insert but with parallel data stream capabilities.​ ​
Performance Considerations: ​ ​ Bypasses SQL layer and uses light appends ​ Constraints, indexes, triggers enabled AFTER load ​ Must perform level 0 archive after load. ​ Possibly faster with large loads, tables that currently have no data, and/or few or no indexes, constraints, or triggers​ ​	Performance Considerations: ​ ​ Transactions are logged ​ Commit Interval can limit transaction size​ ​

http://www-01.ibm.com/support/docview.wss?rs=0&uid=swg21051331