SQL/MX 2.x Reference Manual (G06.24+, H06.03+)

SQL/MX Statements
HP NonStop SQL/MX Reference Manual—523725-004
2-70
Considerations for CREATE SCHEMA
Considerations for CREATE SCHEMA
Duplicate Schema Subvolume
One use of the schema subvolume is to identify all Guardian files in a schema for use
with Guardian-based commands for TMF, RDF or other subsystems. However,
NonStop SQL/MX does not prevent you from specifying a subvolume name that is
already in use by another schema.
If you do, a Guardian wild card of the form \system.$*.subvolume.* will specify
physical files from all schemas using this subvolume name. This might affect your
future ability to refer only to objects in specific schemas when issuing commands to
TMF or RDF.
Reserved Schema Names
Schema names that begin with DEFINITION_SCHEMA_VERSION_ are reserved (in
all catalogs) for system metadata. You cannot create schemas with these names in
user catalogs.
These names are not reserved (you can create schemas with these names in user
catalogs): SYSTEM_SCHEMA, SYSTEM_DEFAULTS_SCHEMA, MXCS_SCHEMA.
Schemas named SYSTEM_SCHEMA, SYSTEM_DEFAULTS_SCHEMA and
MXCS_SCHEMA in the system catalog are reserved for metadata. You cannot drop
them or create objects in them.
Examples of CREATE SCHEMA
•
This example creates a schema:
CREATE SCHEMA mycat.myschema;
•
This example creates a schema with pubs.jsmith as the owner, located on
subvolume ZSDABCDE:
CREATE SCHEMA sch2 AUTHORIZATION 'pubs.jsmith' LOCATION
ZSDABCDE;
•
This example creates a schema located on subvolume ZSDSCHEM:
CREATE SCHEMA myschema LOCATION ZSDSCHEM;