SQL/MP to SQL/MX Database and Application Migration Guide

Overview
HP NonStop SQL/MP to NonStop SQL/MX Database and Application Migration Guide—666211-001
1-4
Planning for Migration
The migrated applications can continue to access SQL/MP database objects, enabling
you to benefit from SQL/MX functionality without converting the SQL/MP database.
Converting SQL/MP applications to SQL/MX applications poses more risk than
creating new SQL/MX applications because some application downtime occurs.
To migrate SQL/MP applications to NonStop SQL/MX, see 4, Converting SQL/MP
Applications to SQL/MX Applications.
Migrating to a New Hardware Platform
When migrating to a new NonStop hardware platform, such as from a NonStop
S-series system to an Integrity NonStop NS-series system, move the existing SQL/MP
applications and databases to the new platform before migrating to NonStop SQL/MX.
For information about migrating to an Integrity NonStop NS-series system, see the
NonStop NS-Series Database Migration Guide.
Migrating within H-series and J-series requires no special considerations for SQL/MX.
Planning for Migration
Before you begin to migrate applications and databases to NonStop SQL/MX, you
must first determine your business objectives and plan the migration. Proper planning
includes:

Determining Your Business Objectives on page 1-4

Assessing Your Current Application and Database Environment on page 1-6

Choosing Which Database Applications and Database Objects to Migrate on
page 1-10

Planning the New Application and Database Environment on page 1-12
Determining Your Business Objectives
Before planning the migration to NonStop SQL/MX, determine your business
objectives, the benefits of the migration to your company, and the potential overall cost.
Qualify the scope of the migration and determine the need for services help. Based on
this information, you can decide if the migration is worth pursuing. Use Table 1-1 to
gather information about your business objectives for the migration.