SQL/MX 2.x Installation and Management Guide (G06.24+, H06.03+)

Reorganizing SQL/MX Tables and Maintaining Data
HP NonStop SQL/MX Installation and Management Guide—523723-004
10-32
Using import to Append Data to Tables or Partitions
Use the import command to append data to multiple partitions of a table. The
DataLoader/MX product can help you streamline this task. DataLoader/MX is a
nonprivileged batch program that provides a library of command routines for loading
and maintaining SQL/MX tables. DataLoader/MX can be customized to perform
data-format transformation while using the import utility for append operations. For
more information about the DataLoader/MX product, see the DataLoader/MX
Reference Manual.
Guidelines for Appending Data to Tables
•
Use the import command to add data to a table or partition without purging
existing data.
•
Use import to add data to SQL/MX tables. You cannot use import to add data
to ASCII, binary, or files other than SQL files.
•
import can use ASCII or binary source files or input files from DataLoader/MX.
•
Use import to insert data into an audited table without resetting the audit
attribute.
•
If an error occurs during an append operation and import is able to terminate
gracefully, no new data is added to the target table for the last transaction run. To
determine if an append operation succeeded, check the listing to see if error
messages occurred.
•
If a processor failure, process failure, BREAK command, or event interrupts an
import operation, import terminates with the table still in a valid state. Rows are
committed based on the -T option if that option is specified. For more information
about import, see the SQL/MX Reference Manual.
Appending Data to Multiple Partitions in Parallel
Use import to append data to partitioned tables in parallel. This strategy can improve
append performance if table partitions are distributed across disks, processors, and I/O
channels. To append data to partitions in parallel:
1. Start an import process for each partition. One way is to start each import
process in the processor associated with the target partition. Another way is to start
import processes in the processors associated with the data sources for the
import command.
2. Issue one import request for each table partition.
3. Supply each import command with the specific range of input data for the target
partition. Possible strategies are:
•
Arrange the input data so that it is divided into separate files, each containing
input for a specific target partition. Use these files as input to import
commands.