MX 3.0 Database and Application Migration Guide (H06.22+, J06.11+)

Considerations for upgrading to SQL/MX Release

3.0

HP NonStop SQL/MX 2.3.x to SQL/MX 3.0 Database and Application Migration Guide—666210-002

2-4

Migrating applications

This section describes the features and limitations related to migration of applications.



SQL/MX Release 3.0 does not support SQL/MX modules and query plans from

earlier versions of SQL/MX.



You must recompile (mxcmp) existing modules on SQL/MX Release 3.0.



You do not need to pre-process, compile the host language, and link when you

migrate from SQL/MX 2.3.x to SQL/MX Release 3.0. However, you might need to

pre-process, compile, and link when you fall back from SQL/MX Release 3.0.

Migrating databases

This section describes the SQL/MX Release 3.0 features and limitations related to

migration of the database, which includes physical data files and all related objects.



Support for databases created on SQL/MX Release 2.x (metadata version 1200).



Support for upgrade of v1200 metadata to SQL/MX Release 3.0 format (v3000).



Support for v3000 schemas in new catalogs without upgrading v1200 metadata

from SQL/MX 2.x version.



Support for new features only with v3000 metadata. No support for new database

features (large rows, large keys, bignum columns) in v1200 schemas.

Upgrading sequence

Figure 2-6 shows the sequence in which you must upgrade from SQL/MX 2.3.x to

SQL/MX 3.0.

Note. BR2 does not pose any separate limitations related to backup and restore of database

objects.

Note. Recompiling programs may result in different execution plans leading to a change in

performance.

Note. Conversion from numeric columns to character columns resulting in truncation fails and

error 8402 is generated. For more information, see Conversions from numeric to char or

varchar on page 2-7.