SQL/MP Installation and Management Guide

Reorganizing Tables and Maintaining Data
HP NonStop SQL/MP Installation and Management Guide—523353-004
8-8
Guidelines for Loading Tables
•
The COPY utility has a DISPLAY FORMAT option that enables you to display data
on your terminal or printer.
•
COPY can write to a tape file.
The APPEND utility appends data to an existing table or to a partition of a key-
sequenced table. The APPEND utility is like the LOAD utility except that it adds data to
a table without purging the existing data. The LOAD and APPEND utilities have similar
options and rules. For more information about APPEND, see Appending Data to Tables
or Partitions on page 8-15.
Guidelines for Loading Tables
When you load tables, consider these guidelines:
•
You cannot use the LOAD command to load an entire audited table. If the table is
audited, you must alter the AUDIT attribute to NO AUDIT before performing the
load. After completing the load, you must alter the AUDIT attribute back to AUDIT
and then make a TMF online dump of the table.
When loading a single partition, you need not alter the AUDIT attribute. You must,
however, do an online dump of the partition when finished with the load to preserve
TMF recovery capability. For more information about loading a single partition, see
Loading Individual Partitions on page 8-9.
•
Each source record of an Enscribe file is written as a row to the target table (or
each row of the source table is written as a target record of an Enscribe file),
overwriting any existing data. The operation must satisfy constraints and provide a
corresponding source column value for all columns defined with NO DEFAULT.
•
If you are loading a table that uses a SYSKEY primary key or a clustering key with
the SYSKEY column appended to the clustering key, the values of the SYSKEY
column will change. If your application has used SYSKEY values, alone or with a
clustering key, as a user-defined embedded linkage field in other tables, a
reloading of the table invalidates your linkage of the tables. Use of a SYSKEY
column, alone or with a clustering key, precludes this reload operation.
•
A relative table uses a relative record pointer. If you load a relative table, the record
automatically compacts, deleting unused slots. To avoid this outcome, use the NO
COMPACT option to retain the relative record locations.
•
Three LOAD parameters control block slack:
°
DSLACK controls the amount of free space in a table’s data blocks.
°
ISLACK controls the amount of free space in a table’s index blocks.
°
SLACK controls the amount of free space in both data and index blocks.
•
LOAD automatically loads any indexes defined for the target table but does not
automatically load any alternate-key files associated with a target Enscribe file.