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-2
Migrating From S-Series Systems to NS-Series
Systems
about installing NonStop SQL/MX, see the SQL/MX Installation and Management
Guide.
Migrating From S-Series Systems to NS-Series Systems
HP strongly recommends that you migrate to an NS-series system, especially if you
are planning to create a SQL/MX database and put it in production. For information
about migrating to an NS-series system, see the
NonStop NS-Series Database
Migration Guide.
Meeting Operating System Requirements
SQL/MX Release 3.0 requires H06.22 or a later RVU, or J06.11 or a later RVU.
SQL/MX Release 2.x requires G06.23 or a later RVU and is not supported on pre-
G06.23 RVUs. For information about the SQL/MX releases that are supported on each
RVU, see NonStop SQL/MX Releases
on page 2-1 and RVUs and Supported SQL/MX
Releases on page 2-6.
Several SQL/MX processes and utilities run in the OSS environment, and most
SQL/MX applications are compiled and executed by default in the OSS environment. If
OSS is not installed on your system, you must install it. For more information, see the
Open System Services Management and Operations Guide.
Planning for Performance and Capacity
Before migrating your database to NonStop SQL/MX, use Measure to obtain initial
baseline data, such as average query run time, CPU time, and process time. At each
phase of the migration, gather the same type of data and analyze it. For intensive
OLTP environments, do performance testing to see if NonStop SQL/MX performs
substantially better than NonStop SQL/MP. For more information about Measure, see
the
Measure User’s Guide. For more information about using Measure during
migration, see Guidelines for Conducting the Migration
on page 1-14.
Before migrating your database to NonStop SQL/MX, check that you have adequate
disk space. Even with adequate disk space, disk contention can be a problem if
multiple databases share the same disk. For minimum disk space requirements for
SQL/MX Release 3.0, see the
SQL/MX Installation and Management Guide. The Disk
Space Analysis Program (DSAP) can help you analyze the use of space on disk
volumes. For more information about DSAP, see the
Guardian Disk and Tape Utilities
Reference Manual.
SQL/MX applications use more memory than SQL/MP applications. If the memory on
your system is less, upgrade to increase the memory. For minimum memory
requirements for NonStop SQL/MX, see the
SQL/MX Installation and Management
Guide.