SQL/MP Reference Manual

HP NonStop SQL/MP Reference Manual—523352-013
L-33
Considerations—LOAD
If you specify more than one configuration file in the PARALLEL EXECUTION
clause, you must specify the FOR index-name clause for each configuration file.
If at least one index is specified in the CONFIG clause, the partitions of any
indexes not specified are loaded in parallel using default configuration values.
Considerations—LOAD

LOAD requires authority to read the source file and to write to the target file. If you
load data to or from a table, you must have authority to read the catalog in which
the table is described. If the target file is a table, LOAD requires the authority to
write to the catalog in which the table is described.

LOAD first purges all data from the target file or table, then begins writing source
records or rows to the target file or table, converting data and reorganizing records
or rows as appropriate.
For full-table loads, LOAD sets the corrupt flag on the base table and indexes
before the load starts. If the operation finishes successfully, LOAD resets the flags.
If the operation fails, the corrupt flag indicates that the file is unusable.
If the target is a table, LOAD automatically loads any indexes on the table after it
loads the table.
When you load a very large key-sequenced file and the data must be sorted, you
might want to use a partitioned scratch file. Use FUP CREATE to create the
scratch file and the SCRATCH option of LOAD to identify it.
If the input records must be sorted, disk space for the sort scratch file and for the
output file must exist concurrently during the sorting phase.

LOAD resembles COPY in that both transfer data from an existing source to an
existing target. The major differences between LOAD and COPY are:

LOAD is typically used to enter initial data into an empty file. COPY is typically
used to add data to a file that already contains data.

LOAD erases or overwrites existing records. COPY does not erase or
overwrite existing records.

LOAD does not write to unstructured files or non-disk files but COPY does.

COPY and LOAD provide the same in-options and move-options, but
LOAD provides additional key-sequence-options for loading
key-sequenced files. These options let you load single partitions, sort output,
and specify the amount of slack to leave in index and data blocks.

COPY is slower than LOAD.

You cannot execute LOAD within a user-defined TMF transaction.
You cannot load data into an audited table. If the table to be loaded is audited, you
must turn auditing off for this table before executing the LOAD utility. If you load a
partitioned table using the PARTONLY option, this restriction does not apply.