SQL/MX 2.x Reference Manual (G06.24+, H06.03+)

SQL/MX Utilities
HP NonStop SQL/MX Reference Manual—523725-004
5-34
Examples of import
[FIXED WIDTH FORMAT]
col=id,1,11
col=company,12,175
col=phone,187,12
col=fax,199,12
RecordLength=66
import Load Command
This import command imports data into the COMPANY table from the fixed width
input file named COINPUT using the format file FORMFILE:
import cat.sch.company -i COINPUT -u FORMFILE -w FIXED
Parallel Load for import
Use parallel load when the destination table is partitioned. Note, when using parallel
load:
•
Some data types require more CPU time during import and therefore parallel load
would be a benefit.
•
Sorting input data by storage key results in faster import time.
•
More processors improves parallel load performance.
You cannot import into one partition in parallel. You receive a locking error if you have
two instances of import loading the same partition.
There are two ways to perform a parallel load:
•
Run multiple instances of import—one for each partition in the destination table—
to load data into a partitioned table by using a single input file. For each import
command, specify the number of input rows (or records), the number of the first
record to import, and the transaction size. The number of the first record to import
begins with zero.
For example, suppose that you partition the EMPLOYEE table into three partitions.
The first partition begins with 0 for the employee number, the second partition
begins with 3000 for the employee number, and the third partition begins with 5000
for the employee number.
Note. You must specify the transaction size for better performance. If you do not, import
issues a warning regarding performance for other import processes running on the same
table because auditing might be turned off for all the partitions by the first import process if
the table is empty and does not have any indexes. This strategy enables the first import
process to use a fast loading technique. However, the performance of the parallel import
processes on the remaining partitions is affected, because auditing for all the partitions is
off, and the table contains data as a result of the first import operation.