SQL/MP Installation and Management Guide

Moving a Database
HP NonStop SQL/MP Installation and Management Guide—523353-004
9-17
Moving Tables
COPY and LOAD do not move dependent objects automatically except any indexes
that are defined on the table. Both COPY and LOAD require that you create the new
table before copying or loading the data. For additional information on copying or
loading tables, see Section 8, Reorganizing Tables and Maintaining Data, or the
SQL/MP Reference Manual.
Using BACKUP and RESTORE
When you use BACKUP and RESTORE to move a table, the utilities attempt to
duplicate all partitions, indexes, and protection views. Shorthand views are duplicated
only if you explicitly name them in the file set list. If you use a wild-card string for the
file set list, any shorthand view names identified in the wild-card string are treated as if
you had explicitly named them.
To move all these objects, specify the MAP NAMES option so that RESTORE can map
the dependent source objects to the target objects. In addition, RESTORE writes all
constraints, comments, and statistical information to the appropriate tables of the target
catalog.
The DUP and BACKUP/RESTORE utilities enable you to specify the source tables by
name or by qualified file-set list. If the table and its dependent objects all reside on the
same subvolume and are moved to another subvolume, you can use a target file-set
list to specify the new location. If the table and its dependent objects are to reside on
two or more subvolumes, you must use the MAP NAMES option.
You cannot use the MAP NAMES option and the target file-set list in the same
command. If the dependent objects are described in a new catalog, use the CATALOG
clause to define the new catalog for the objects.
If you want to move a table to a new subvolume on the same volume or to rename the
table, you can use the ALTER TABLE statement with the RENAME option. By using
this approach, you do not actually move the data, but you alter the directory entry and
all associated catalog references to the table.
The moving utilities do not automatically move dependent programs with the
underlying table. Programs are moved automatically only if they are included in the file
set list. After you have moved a table, you should include steps to explicitly SQL
compile the dependent programs to avoid automatic recompilation. Programs are not
invalidated by the moving operation but will be invalidated when the old table is
dropped.