MX Database and Application Migration Guide

Preparing to Migrate From NonStop SQL/MP to

NonStop SQL/MX

HP NonStop SQL/MP to NonStop SQL/MX Database and Application Migration Guide—666211-001

3-3

Planning for Fallback

Before you migrate to NonStop SQL/MX, plan for a potential fallback to NonStop

SQL/MP. To ensure that you can fall back more easily, follow these guidelines:



Planning New Feature Implementation on page 3-3



Keeping SQL/MP Applications, Database Objects, and Metadata on page 3-3

If you encounter a serious problem with NonStop SQL/MX and need to fall back to a

SQL/MP environment, see 6, Falling Back to NonStop SQL/MP

Planning New Feature Implementation

Before using the SQL/MX features, ensure that each system node has the supported

release version of NonStop SQL/MX. The simplest approach is to ensure that all

relevant nodes have the same release of NonStop SQL/MX. After you successfully

install NonStop SQL/MX on all relevant nodes and verify that it works satisfactorily, you

can use the features of NonStop SQL/MX on those nodes. This strategy effectively

separates the installation phase from the feature development and utilization phase. If

fallback becomes necessary, it is most likely to occur during or shortly after the

installation phase, before you start using new features.

Keeping SQL/MP Applications, Database Objects, and Metadata

If you are migrating to SQL/MX Release 3.0 from a SQL/MP database environment, do

not delete the SQL/MP applications, database objects, and metadata until you are

certain that you do not need to fall back. Deleting these objects prevents a successful

fallback.

Preserve the source files of SQL/MP applications and the compiled executables in a

safe place.

Installing SQL/MX

Install the latest version of SQL/MX that is supported by the RVU of the system. For

more information, see NonStop SQL/MX Releases

on page 2-1 and RVUs and

Supported SQL/MX Releases on page 2-6.

Be aware that installing a SQL/MX release on your system overwrites the previous

SQL/MX release. Although NonStop SQL/MP and NonStop SQL/MX can exist on the

same node, only one release of SQL/MX software can exist on a node at a time. For

example, if SQL/MX Release 3.0 is installed on a node, SQL/MX Release 2.2 or

SQL/MX Release 2.0 cannot be installed at the same time.

Note. When using new features, if you encounter problems that are specific to NonStop

SQL/MX, consider discontinuing the use of those features instead of falling back.