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

Introduction

HP NonStop SQL/MX Reference Manual—523725-004

1-23

Naming Objects

Refer to SQL/MP database objects through MXCI or through applications by using

either physical names, logical names, or DEFINE names, as described next. For more

information, see Database Object Names on page 6-12, Object Naming on

page 10-47, or DEFINEs on page 6-36.

Physical Names

NonStop SQL/MP uses Guardian names as names for SQL tables, views, indexes,

partitions, collations, and program modules. A portion of the Guardian name (the

subvolume name) is used as an SQL/MP catalog name.

To provide flexibility, NonStop SQL/MX provides support for Guardian four-part object

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, view,

index, partition, collation, or program module.

For information about Guardian name resolution, see Attribute Value NSK for Guardian

Names and Guardian Name Resolution on page 10-49.

Logical Names

To move toward full ANSI SQL:1999 compliance, NonStop SQL/MX provides support

for three-part logical object names of the form:

[[catalog.]schema.]name

In this three-part name, catalog is the first part of the name, schema is the second

part of the name, and table is the third part of the name. See Catalogs on page 6-2

and Schemas

on page 6-104.

For information about logical name resolution, see Attribute Value ANSI for Logical

Names on page 10-49.

Alias Mappings

To permit the use of logical names, a user table named OBJECTS stores alias names.

The MP_PARTITIONS table stores mappings from logical object names to physical

Guardian locations. See OBJECTS Table on page 10-18 and MP_PARTITIONS Table

on page 10-18.

To create the necessary mappings from logical to physical names, use the CREATE

SQLMP ALIAS statement:

CREATE SQLMP ALIAS catalog.schema.table

[\node.]$volume.subvol.filename