SQL/MX 2.x Installation and Management Guide (G06.24+, H06.03+)

Creating an SQL/MX Database
HP NonStop SQL/MX Installation and Management Guide—523723-004
7-2
Preparing to Create Your SQL/MX Database
•
Use either valid SQL/MP aliases or Guardian names for SQL/MP objects.
•
Make sure that all SQL/MP objects comply with the Guardian security conventions
as described in the SQL/MP Installation and Management Guide.
•
You can mix SQL/MP and SQL/MX tables in the same DML statement. You can
join an SQL/MP and SQL/MX table, create a union of them, and insert data from an
SQL/MP table into an SQL/MX table and visa versa.
•
You cannot create a view that references both an SQL/MP table and an SQL/MX
table.
For more information about the differences and similarities between NonStop SQL/MX
and NonStop SQL/MP, see the SQL/MX Comparison Guide for SQL/MP Users.
For instructions and examples on executing DDL statements from SQLCI, see the
SQL/MP Installation and Management Guide and the SQL/MP Reference Manual.
Preparing to Create Your SQL/MX Database
Before you begin to create your SQL/MX database, first plan the database and define
its layout as described in Section 4, Understanding and Planning SQL/MX Tables. Also
plan your security, TMF requirements, RDF requirements, and recovery mechanisms
as described in Section 5, Planning Database Security and Recovery.
After you create the database, you can load the data into the SQL/MX tables, compile
your application programs, and start running your applications. For information on
managing database applications and modules, see Section 11, Managing Database
Applications.
SQL/MX Subvolume and File Naming
Guidelines
Before you build your SQL/MX database, familiarize yourself with the rules for naming
SQL/MX subvolumes and files. These rules are always followed when NonStop
SQL/MX generates file names and are enforced by NonStop SQL/MX for user-
specified names. These rules are in addition to Guardian naming rules already
enforced by the Guardian file system.
SQL/MX Subvolume Naming Guidelines
•
The subvolume name must begin with the letters ZSD.
•
The character following ZSD must be a letter, not a digit (for example, ZSDa, not
ZSD2).
Note. NonStop SQL/MX additionally restricts system-generated names by excluding vowels to
prevent names containing actual words that could be unexpected or misleading.