SQL/MP Installation and Management Guide

HP NonStop SQL/MP Installation and Management Guide—523353-004
9-1
9 Moving a Database
The guidelines required for moving a database depend on knowing the current
database scheme used at each site. The database administrator should analyze all the
factors and develop a plan before attempting to move a database.
Reasons for Moving a Database
The reason for moving a database usually falls into one of these categories:
•
Moving objects to enhance performance
This category might include moving objects to another volume, splitting or moving
partitions across different volumes, or redefining partition row boundaries for tables
and indexes.
•
Adding or changing equipment
This category might include moving objects to new volumes, partitioning tables and
indexes, or restoring a volume following an equipment change.
•
Moving objects from one application development phase or group to another, such
as moving the database and application programs from development to production
The move can be from one subvolume to another, from one volume to another, or
from one node to another.
•
Moving objects from one node to another, such as the release of software to an
end-user node.
This category includes the creation of new catalogs, the creation or moving of the
database, and the SQL compilation of application programs.
•
Moving objects from a node running an older version of SQL/MP software to a
node running a newer version.
This category involves a series of staged operations and testing, described in the
SQL/MP Version Management Guide.
Moving a database involves moving a set of SQL catalogs and objects from one
environment to another. For example, if you move a catalog or any of its objects, you
probably want to move the objects and all the definitions and relations associated with
those objects.