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

Introduction to SQL/MX Database Management
HP NonStop SQL/MX Installation and Management Guide—544536-007
1-7
Guardian Physical Names
You name tables, views, and other SQL/MX objects by using a three-part ANSI logical
name:
catalog-name.schema-name.object-name
In this three-part name, catalog-name is the name of the catalog, schema-name is
the name of the schema, and object-name is the simple name of the object. Each of
the parts is an SQL identifier.
NonStop SQL/MX automatically qualifies an object name with the current default
catalog and schema name unless you explicitly specify catalog and schema names
with the object name. These terminology guidelines apply to ANSI names:
•
A fully qualified or three-part ANSI name uses all three of its parts
(catalog-name.schema-name.object-name).
•
A two-part ANSI name omits the catalog name (schema-name.object-name).
•
A one-part or simple ANSI name omits the catalog and schema names
(object-name).
The two-part name schema-name.object name is qualified implicitly by the current
default catalog. The one-part name object-name is qualified implicitly by the default
schema and catalog.
For more information about ANSI names, see the SQL/MX Reference Manual.
Guardian Physical Names
The underlying Guardian physical names of SQL/MX objects and SQL/MP objects are
qualified with the system node, volume, and subvolume names. For example, SQL/MP
tables and views are created with Guardian physical names of the form:
[\node.] [[$volume.]subvol.]filename
In this four-part name, \node is the name of a node on an HP NonStop system,
$volume is the name of a disk volume, subvol is the name of a subvolume, and
filename is the name of a Guardian disk file or the name of an SQL/MP table or view.
SQL/MX data is stored in files with Guardian physical names. In turn, these files are
associated with ANSI names.
For information about using Guardian physical names for SQL/MP objects, see the
SQL/MP Reference Manual and the SQL/MP Installation and Management Guide.
DEFINE Names
Use class MAP DEFINE names as logical names for SQL/MP tables or views in DML
statements. When NonStop SQL/MX compiles such statements, it replaces the
DEFINE name in the statement with the associated Guardian physical name. You can
create DEFINE names within MXCI or names can be inherited from the TACL process
or the OSS shell.