MX 3.0 Database and Application Migration Guide (H06.22+, J06.11+)

HP NonStop SQL/MX 2.3.x to SQL/MX 3.0 Database and Application Migration Guide—666210-002

1-1

1 Overview of SQL/MX Migration

This section introduces the process of migrating to NonStop SQL/MX and discusses

these topics:



Migration Terminology on page 1-1



Upgrading to SQL/MX Release 3.0 on page 1-1



Planning for Migration on page 1-2



Guidelines for Conducting the Migration on page 1-2



Assistance With Migration on page 1-4

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.0. SQL/MX Release 3.0, 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 NonStop SQL/MX, such as upgrading from SQL/MX Release 2.3.x to

SQL/MX Release 3.0.

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 NonStop SQL/MX, such as downgrading from SQL/MX

Release 3.0 to SQL/MX Release 2.3.4.

Upgrading to SQL/MX Release 3.0

If you are currently using NonStop SQL/MX, you might want to upgrade to a newer

version to obtain bug fixes, performance enhancements, and new functionalities.

Upgrading to SQL/MX Release 3.0 involves the following:



SQL/MX programs or associated module files must be recompiled. With one

possible exception, no other changes are required. In SQL/MX Release 3.0, ANSI