SQL/MP Installation and Management Guide

Format 2 Partitions
HP NonStop SQL/MP Installation and Management Guide—523353-004
C-7
Operational Considerations for SQL Format
2-Enabled Table Use
establishes a point in time with which to compare performance prior to migration
and enables you to manage the performance impact of future growth separately
from migration.
•
Network environment
Users with multiple Expand nodes must upgrade nodes that contain tables and
views that span network nodes to the G06.13 RVU and upgrade catalogs to
version 350. Version 350 tables and views are inaccessible from systems running
software earlier than the G06.13 RVU. The Backup/Restore product is
interoperable between the G06.13 (SQL/MP Format 2 partition enabled) and
earlier RVUs. The Backup/Restore product reports errors when it attempts to
access a Format 2 SQL object from a pre-G06.13 RVU system. If you specify a
wild-card file set, Format 2 SQL objects are skipped.
Operational Considerations for SQL
Format 2-Enabled Table Use
Before using any Format 2-enabled tables on your system, you should understand the
operational, interoperability, and fallback considerations associated with their use.
Then, you should formulate a plan that controls their introduction onto your system and
minimizes the risk to your data in the various possible fallback scenarios.
The operational considerations for using SQL Format 2-enabled tables are:
•
The Format 2-enabled feature can be used only with key-sequenced tables.
•
Before you make the changes described in the next two bullets, you might want to
take new TMF online dumps or backups of the SQL catalogs and tables involved,
to provide additional fallback protection. You should include all the partitions of the
involved tables, not just the partitions that will become Format 2, in addition to all of
their associated index partitions and views.
•
Before you introduce any SQL Format 2-enabled tables to your system, you must
upgrade all the SQL catalogs in which their partitions will be registered to version
350.
•
After you upgrade the catalogs, you can create new Format 2-enabled tables using
the SQLCI CREATE TABLE command, and you can change existing Format 1
enabled tables to Format 2-enabled by using the SQLCI ALTER TABLE command.
When you alter a table to Format 2-enabled, its partitions remain Format 1. You
can then create new Format 2 partitions or individually data-migrate Format 1
partitions to Format 2, by using the ALTER TABLE command, with or without
SHARED ACCESS. The shared access option allows your applications to update
the table while this operation takes place.
When you alter a table to Format 2-enabled, the labels of all its table partitions and
of all the associated index partitions and views are changed to version 350. In
addition, the partition array structure in the labels of each table partition and index
partition is reformatted.