SQL/MX 2.x Database and Application Migration Guide (G06.23+, H06.04+, J06.03+)

Overview of SQL/MX Migration
HP NonStop SQL/MX Database and Application Migration Guide—540435-005
1-5
Migrating From NonStop SQL/MP to NonStop
SQL/MX
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 Section 10, Converting
SQL/MP Applications to SQL/MX Applications.
Migrating SQL/MP Database Objects to NonStop SQL/MX
You do not need to migrate SQL/MP database objects to SQL/MX database objects
because NonStop SQL/MX supports simultaneous access to both SQL/MP and
SQL/MX database objects. However, in some situations, you might find it necessary to
migrate some or all SQL/MP tables to SQL/MX tables. For example, you might want
your database to use triggers, referential integrity constraints, or hash partitioning,
which NonStop SQL/MP does not support.
Before migrating data from SQL/MP tables to SQL/MX tables, convert the SQL/MP
applications that reference those tables to SQL/MX applications. Converting SQL/MP
database objects to NonStop SQL/MX poses more risk than migrating only SQL/MP
applications because downtime occurs for both the database and applications.
To migrate SQL/MP database objects to NonStop SQL/MX, see Section 11, Converting
an SQL/MP Database to SQL/MX Tables.
Phased Versus Rapid Migration to NonStop SQL/MX
When migrating from NonStop SQL/MP to NonStop SQL/MX, you can choose either a
phased approach or a rapid approach, depending on your business needs.
Figure 1-3. Migrating SQL/MP Database Objects to SQL/MX Database Objects
SQL/MX
Application
SQL/MX
database
VST005.vsd
SQL/MP
database
Migrating the database
SQL/MP
Application
Migrating the application