SQL/MX 3.2 Management Manual (H06.25+, J06.14+)

By using the syntax last partition in the example, you avoid the need to specify the last
partition by its location.
Example of Moving an Existing Hash Partition to a New Location
You need to use $DATA03 for other purposes. Use the MODIFY command to move the index
partition there to another volume:
MODIFY INDEX cat2.sch2.ordersr_via_ordernumber
move
where location $data03
to location $data05;
Managing System-Clustered Tables and Indexes
A system-clustered table or index has no primary key and no STORE BY clause. Its primary key
defaults to the SYSKEY.
You can use MODIFY to move the existing partition of a system-clustered table or index to a new
location. A system-clustered table can have only a single partition. Only offline partition operations
are supported.
For system-clustered partitions, MODIFY supports moving an entire system-clustered partition to a
new location.
Using MODIFY in a System-Clustered Partition
For this system-clustered partition example, suppose that the table ORDERSSC has been created
in this way:
CREATE TABLE cat4.sch4.orderssc
(location char(16) not null not droppable,
ordernumber integer unsigned not null not droppable,
ordertime timestamp)
location $DATA09;
Example of Moving an Entire System-Clustered Partition to a New Location
You need to use $DATA09 for other purposes. You decide to move the system-clustered table
ORDERSSC to a different volume. Use this MODIFY TABLE command to move the table to the
volume $DATA03:
MODIFY TABLE cat4.sch4.orderssc move partition
to location $DATA03;
Using import to Load SQL/MX Tables
Use the import command to move data from an input file in ASCII or UCS2 format into an
existing SQL/MX table. For example, you would use import to load an input file that contains
the ASCII-formatted contents of another vendor’s SQL table into an SQL/MX table. DataLoader/MX
can also send output to an import process.
Guidelines for Using import
• The input data file and the table must already exist before you can import the data into table.
import does not create the files or tables.
• import adds data to a table without purging existing data.
• Whenever possible, import automatically loads data into an empty table by using a special
fast loading technique designed specifically for NonStop SQL/MX.
• import automatically loads dependent indexes while loading the table rows. Performance
considerations for loading dependent indexes are described in “Managing Indexes to Improve
import Performance” (page 197).
Using import to Load SQL/MX Tables 191