Вы находитесь на странице: 1из 1

Import Utility Load Utility

Slow when moving large amounts of data. Faster than the import utility when moving large
amounts of data, because the load utility writes
formatted pages directly into the database.

Limited exploitation of intra-partition Exploitation of intra-partition parallelism. Typically, this


parallelism. requires symmetric multiprocessor (SMP) machines.

No FASTPARSE support. FASTPARSE support, providing reduced data


checking of user-supplied data.

Supports hierarchical data. Does not support hierarchical data.

Creation of tables, hierarchies, and indexes Tables and indexes must exist.
supported with PC/IXF format.

WSF format is supported. WSF format is not supported.

No BINARYNUMERICS support. BINARYNUMERICS support.

Supports import into tables and views. Supports loading into tables only.

All rows are logged. Minimal logging is performed.

Trigger support. No trigger support.

All constraints are validated during an import The load utility checks for uniqueness and computes
operation. generated column values, but all other constraints
must be checked using SET INTEGRITY.

The key values are inserted into the index The key values are sorted and the index is built after
one at a time during an import operation. the data has been loaded.

You can import into a host database through You cannot load into a host database.
DB2 Connect.

Import files must reside on the node from In a partitioned database environment, load files or
which the import utility is invoked. pipes must reside on the node that contains the
database. In a non-partitioned database environment,
load files or pipes can reside on the node that contains
the database, or on the remotely connected client from
which the load utility is invoked.

R.N. Sangwan www.hometutor.net.in Ph. 9312406920