Working with v3500, v3400, v3200, v3100, and v3000 objects
The schema version for R3.5 is v3500. In Release 3.5, a catalog can contain v3000, v3100, v3200, v3400, or v3500 schemas, but not a mixture of the versions. Note that there is no v3300 schema;
-
SQL/MX R3.4 is the last release that includes general support for v1200 schemas and metadata. v1200 schemas will not be generally supported in the next subsequent release after SQL/MX R3.4 but it is possible to upgrade v1200 metadata to the latest version.
-
Starting from SQL/MX 3.5, you will no longer be able to use v1200 schemas, which means any existing v1200 schema must be upgraded to v3000 or later schemas.
If you are using MXDM client, and to continue to use it with R3.5, you must upgrade the schema to minimum v3200 version as the minimum supported metadata schema version for MXDM is 3200.
A CREATE SCHEMA statement creates a new schema of the same version as those schemas that already exist 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 empty catalogs are with version v3500. You do not have to perform additional steps to create v3500 schemas.
You must perform these additional steps only when a v3000 or v3100 or v3200 or v3400 schema is required in a new catalog that does not already contain any schema.
For example, to create a v3100 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 '3100'
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 the SQL/MX Reference Manual.