SQL/MX 3.1 Database and Application Migration Guide (H06.23+, J06.12+)

HP NonStop SQL/MX Release 3.1 Database and Application Migration Guide—663853-001
1-1
1 Overview of SQL/MX Migration
This section introduces the process of migrating to SQL/MX Release 3.1 and
discusses the following topics:

Migration terminology on page 1-1

Planning for migration on page 1-1

Guidelines for conducting the migration on page 1-2

Assistance with migration on page 1-3
Migration terminology
You must be familiar with the following terms, which are used throughout the manual:
Version. A product version or the version of a software component.
Release. The product version of NonStop SQL/MX. A SQL/MX release identifies a set of
SQL/MX products as belonging to a given version of NonStop SQL/MX.
SQL/MX application. Uses SQL/MX syntax, is SQL-compiled using MXCMP, and can query
SQL/MP and SQL/MX database objects.
SQL/MX Release 2.x. SQL/MX Release 2.0, SQL/MX Release 2.1, SQL/MX Release 2.2,
and subsequent releases until otherwise indicated in a replacement publication.
SQL/MX Release 3.x. SQL/MX Release 3.0, SQL/MX Release 3.1, and subsequent
releases unless otherwise specified.
Upgrade (also known as Migration). Moving from an older software version to a newer
software version. For example, you upgrade to a newer incremental or maintenance
release of SQL/MX, such as upgrading from SQL/MX Release 2.3.x to SQL/MX
Release 3.1.
Downgrade (also known as Fallback). Reverting from a newer software version to an
older software version. For example, you downgrade to an older incremental or
maintenance release of SQL/MX, such as downgrading from SQL/MX Release 3.1 to
SQL/MX Release 2.3.4.
Planning for migration
You must save a copy of the modules before a system upgrade. If you fall back to the
current version at a later stage, you can reinstate this copy after fallback. This method
is applicable only if the database layout after the fallback is similar to the layout before
the system upgrade.