SQL/MP to SQL/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-4
Installing Corequisite Independent Products
Ordering the SQL/MX DDL License
To create SQL/MX database objects, you must purchase and install the SQL/MX DDL
license, product T0394. You cannot create SQL/MX database objects without this
product. If you try to create SQL/MX database objects without the DDL license,
NonStop SQL/MX returns an error message informing you that the system is not
licensed.
Installing Corequisite Independent Products
Order any corequisite independent products for the version of SQL/MX Release 3.0
that you install on your system. Some corequisite independent products include:

RDF

NonStop Server for Java

JDBC Driver for SQL/MX
For more information, see the
H06.nn or J06.nn Release Version Update
Compendium.
Preparing to Migrate SQL/MP Applications
Decide which SQL/MP applications to convert to SQL/MX applications. For more
information, see Converting SQL/MP Applications to SQL/MX Applications
on page 4-1
and Reasons for Keeping SQL/MP Applications
on page 4-5.
Planning activities for migrating applications depend on your development environment
and on the types of applications that you are currently using. See Types of SQL/MP
Applications to Convert on page 4-6.
Determine whether the migrated applications will continue to query SQL/MP database
objects or whether they will query new SQL/MX database objects. If you plan to
migrate SQL/MP database objects to NonStop SQL/MX, see Preparing to Migrate
SQL/MP Database Objects.
Preparing to Migrate SQL/MP Database
Objects
Decide which SQL/MP database objects to migrate to NonStop SQL/MX. For more
information, see Converting SQL/MP Tables to SQL/MX Tables
on page 5-1 and
Reasons for Keeping SQL/MP Tables
on page 5-3.
Determine the amount of disk space and the CPU usage that the new SQL/MX
database will require. For more information, see Planning for Performance and
Capacity on page 3-2.
While converting a SQL/MP database to SQL/MX tables, be prepared for disruption to
applications that access the tables. Determine the required changes to those