SQL/MX 2.x Installation and Management Guide (G06.24+, H06.03+)

Migrating an SQL/MP Database to NonStop SQL/MX
Release 2.1 or Release 2.0
HP NonStop SQL/MX Installation and Management Guide—523723-004
14-2
Planning for Migration
•
SQL/MP and SQL/MX software can reside on the same node. However, multiple
releases of NonStop SQL/MX cannot reside on the same node. Only one release
of SQL/MX software can reside on a node. For example, if Release 2.1 is installed
on a node, Release 2.0 or Release 1.8 cannot be installed at the same time.
•
Migration from Release 1.8 to Release 2.1 or Release 2.0 is largely a manual
process. No tool is available that can perform all the migration steps from start to
finish. However, the migrate utility automates the process of migrating certain
Release 1.8 metadata.
•
For SQL/MP tables used with Release 1.8, you must migrate certain MPALIAS
metadata elements before you can use these tables with Release 2.1 or Release
2.0. Migrating an Enscribe Database to Release 2.1 or Release 2.0 Using SQL/MX
Tables on page 14-14 describes how to migrate MPALIAS metadata using the
migrate utility.
•
Fallback to SQL/MX releases earlier than Release 1.8 is not supported. If you are
using an SQL/MX release earlier than Release 1.8, you must migrate to an RVU
that supports Release 1.8 (G06.18 through G06.22) before migrating to Release
2.1 or Release 2.0 (G06.23 or later).
•
After metadata migration, some applications, either SQL/MP or SQL/MX-based,
run unchanged in the Release 2.1 or Release 2.0 environment. Others require
recompiling. If SQL/MX tables are created from that environment, applications
must be rewritten and recompiled to access the new tables. For application
migration information, see Section 11, Managing Database Applications.
•
In multinode installations, where queries must access data on other nodes, all
Release 1.8 nodes must migrate to Release 2.1 or Release 2.0 at the same time.
A mixture of nodes running Release 1.8 and Release 2.1 or Release 2.0 is not
supported.
Planning for Migration
Planning ahead for database migration should include planning to migrate applications,
planning for performance, planning for installation, and planning for fallback.