SQL/MX 2.3.x to SQL/MX 3.0 Database and Application Migration Guide (H06.22+, J06.11+)

Version Management and Interoperability
HP NonStop SQL/MX 2.3.x to SQL/MX 3.0 Database and Application Migration Guide—666210-002
3-11
Interoperability Across Schema Versions
compiled the module. The SQL/MX Release 3.0 compiler produces the module version
3000.
For a 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 v1200 schemas, v3000 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.

Immediately after upgrading from SQL/MX Release 2.3.x to SQL/MX Release 3.0,
the version of the system schema and all user schemas is 1200. UPGRADE ALL
METADATA will upgrade all metadata for the system schema and the user
schemas to version 3000. After the metadata is upgraded to version 3000, you
cannot create v1200 schemas in catalogs that contain v3000 schemas. However,
using the
control query default (cqd) command, you can create v1200
schemas in catalogs that do not already contain v3000 schemas.

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 are able 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.
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.