SQL/MX 3.1 Database and Application Migration Guide (H06.23+, J06.12+)

Considerations for upgrading to SQL/MX Release
3.1
HP NonStop SQL/MX Release 3.1 Database and Application Migration Guide—663853-001
2-3
Working with v3100, v3000, and v1200 objects in
SQL/MX Release 3.1
Working with v3100, v3000, and v1200 objects
in SQL/MX Release 3.1
In SQL/MX Release 3.1, a catalog can contain v1200, v3000, or v3100 schemas, but
not a mixture of the versions.
A CREATE SCHEMA statement will create a new schema of the same version as
those schemas in the catalog. For example, suppose that a catalog contains some
v3000 schemas. The version of a new schema that is created in that catalog will be
3000.
By default, schemas created in new catalogs will be v3100. You do not have to perform
additional steps to create v3100 schemas.
You must perform these additional steps only when a v1200 or v3000 schema is
required in a new catalog that does not already contain any schema.
To create a v3000 schema in a new catalog, you must enter the following control
query default command before you issue the CREATE SCHEMA statement:
control query default create_definition_schema_version '3000'
To create a v1200 schema in a new catalog, you must enter the following control
query default command before you issue the CREATE SCHEMA statement:
control query default create_definition_schema_version '1200'
If the system schema version is 3000 or later, you cannot create a v1200 schema.
After executing the UPGRADE ALL METADATA command, you cannot create v1200
schemas.
Irrespective of the schema version, no explicit action is needed to create or maintain
individual database objects such as tables, indexes, and views.
For more information on commands, see SQL Statements in the SQL/MX Release 3.1
Reference Manual.
Conversions from numeric to char or varchar
SQL/MX Release 3.x reports 8402 errors during conversions from numeric to char or
varchar types with truncation. In SQL/MX Release 2.x, such conversions truncate the
data without any errors.
The following examples illustrate overflow errors generated in SQL/MX Release 3.x: