SQL/MX 2.x Database and Application Migration Guide (G06.23+, H06.04+, J06.03+)

Converting an SQL/MP Database to SQL/MX Tables
HP NonStop SQL/MX Database and Application Migration Guide—540435-005
11-3
Size of the Database Object
your database consists of relative tables and you want to use features in NonStop
SQL/MX, you might consider converting your database to SQL/MX tables.
Size of the Database Object
NonStop SQL/MP limits the number of partitions that can exist for an SQL/MP table.
However, NonStop SQL/MX does not limit the number of partitions for an SQL/MX
table. If your SQL/MP table is growing and becomes too big for NonStop SQL/MX, you
might consider converting the SQL/MP table to NonStop SQL/MX.
Reasons for Keeping SQL/MP Tables
In some cases, it might be preferable to keep SQL/MP tables instead of converting
them to SQL/MX tables. If you do not need to use new SQL/MX features, you do not
need to migrate to NonStop SQL/MX. The next subsections describe some of the
reasons for keeping SQL/MP tables.
DEFINE Names
NonStop SQL/MX does not support DEFINE names for SQL/MX database objects.
Local Node Autonomy
NonStop SQL/MX has limited local node autonomy for distributed databases. In
NonStop SQL/MX, you cannot replicate the metadata of an SQL/MX database object
on each node where the object is partitioned. The SQL/MX metadata resides only on
the node where the SQL/MX database object was created. For more information about
managing a distributed SQL/MX database, see the
SQL/MX Installation and
Management Guide.
Online Manageability
NonStop SQL/MX does not currently support online index creation with concurrent
read and update capability. However, the SQL/MX POPULATE INDEX utility supports
offline index creation.
NonStop SQL/MX also does not currently support online partition management for
tables and indexes that are hash-partitioned. However, NonStop SQL/MX does support
offline partition management of these objects. Online partition management of range-
partitioned tables and indexes is supported and is equivalent to the SQL/MP ALTER
TABLE WITH SHARED ACCESS statement. For more information about partition
management, see the
SQL/MX Installation and Management Guide.
Partition Management
In NonStop SQL/MX, the first or second half of a partition can be split off into a new
partition. However, a partition cannot be split into two new partitions in a single
operation, which NonStop SQL/MP supports. NonStop SQL/MX requires two steps: