FastSort Manual

Sorting From NonStop SQL/MP
FastSort Manual—429834-003
8-15
Configuring a LOAD Statement
== $DATA4.SALES.AGEINDEX
== $DATA5.SALES.AGEINDEX
== \NEWYORK.$DATA2.SALES.AGEINDEX
\NEWYORK.$DATA3.SALES.AGEINDEX
== Set up a default priority for the RECGEN processes:
CREATEINDEX BASETABLE DEFAULT PRI ( 140 )
CREATEINDEX BASETABLE DEFAULT \NEWYORK PRI ( 140 )
== Set up a default pool of scratch files for the sort
== processes.
CREATEINDEX INDEX DEFAULT SCRATCH ($TEMP1, $TEMP2, $TEMP3)
CREATEINDEX INDEX DEFAULT \NEWYORK SCRATCH ($TEMP4)
== Request that overflow scratch files avoid certain disks--
== those specified plus $SYSTEM and TMF audit trail disks.
CREATEINDEX DEFAULT NOSCRATCHON ($SYS*,$WORK*)
== Request that overflow scratch files use specific disks
== on the remote node
CREATEINDEX INDEX DEFAULT \NEWYORK SCRATCHON ($TEMP*)
== Request that the $data3 sort process use $TEMP7 for
== scratch files.
CREATEINDEX \NEWYORK.$DATA3 SCRATCH ($TEMP7)
== End of configuration file.
Loading Multiple Indexes
PARALLEL EXECUTION ON applies to only one partitioned index at a time. If the base
table has more than one partitioned index, the partitions of the first index are loaded
first. After the first index is loaded, the partitions of the second index are loaded in
parallel, and so on.
You can use the FOR index-name clause of the CONFIG option to specify a
separate configuration file for each index. If you omit this clause, the configuration file
applies to all indexes on the base table. If you specify at least one index in the FOR
clause, SQL/MP parallel loads the partitions of any index not specified with the default
configuration values. For more information about CONFIG option syntax, see LOAD
entry in the SQL/MP Reference Manual.
Configuring a LOAD Statement
LOAD is a SQLCI utility you use to load data. LOAD can transfer data from an SQL/MP
table or a disk file into either an SQL/MP table and its indexes or an Enscribe
structured disk file. LOAD overwrites existing data in the target table or file.
Caution. To use LOAD you must turn off auditing for the table being loaded. This action
invalidates TMF online dumps of the table and its indexes. To ensure TMF rollforward
protection for the table and its indexes, make new online dumps of all table and index
partitions. If you load only partitions rather than an entire table, turn off auditing and make new
online dumps for only the partitions being loaded.