MX Database and Application Migration Guide

Version Management and Interoperability

HP NonStop SQL/MP to NonStop SQL/MX Database and Application Migration Guide—666211-001

2-11

Interoperability Across Schema Versions

Module Versions

When you compile user modules of embedded SQL/MX applications, the version

assigned to a module is the same as the default compiler version of the node where

you compile the module. The SQL/MX compilers produce the following module

versions:

For a user module to be executed on a node, the module version must be higher than

or equal to the earliest supported plan version and lower than or equal to the current

plan version. Otherwise, NonStop SQL/MX returns a versioning error.

Interoperability Across Schema Versions

NonStop SQL/MX Release 3.0 is compatible with version 1200 schemas and version

3000 schemas, and the objects in such schemas, on the local node and on remote

compatible nodes in a network.

Limitations to Schema Version Interoperability



Version 1200 schemas and version 3000 schemas cannot co-exist in a catalog.



Database relationships cannot cross schema versions. For example, a view in a

version 1200 schema cannot reference a table in a version 3000 schema. The

following types of database objects have the capability to establish cross schema

relationships:



views



triggers



RI constraints

If you attempt to establish cross-schema relationships between version 1200 and

version 3000 schemas, the relationship will be rejected with error 25209.

SQL/MX Compiler User Module Version

SQL/MX Release 3.0 compiler 3000

Note. SQL/MX Release 3.0 supports version 3000 plans or modules only. You must recompile

all modules on SQL/MX Release 3.0 before executing them.