MX Release 3.2 (H06.25+, J06.14+)

ManualsBrandsHP ManualsServerHP Integrity NonStop J-Series

The following table lists the relationships between the database object names:

Corresponding SQL/MX 3-part database name based on

ANSI SQL 92 standard

NonStop ODBC Server 3-part database name based on SQL

Server implementation

CatalogDatabase name

SchemaOwner

Object nameObject name

In the NonStop ODBC Server, a database name is in the form:

system-name_volume-name_subvolume-name

The system_name is the name of the NonStop system without the backslash (\). The volume_name

is the name of the volume without the dollar sign ($), and subvol_name is the name of the

subvolume. Do not use periods between the names because the name represents one logical name

for each catalog and schema.

ODBC metadata information (through ODBC Catalog APIs) is returned based on the values for

each of the three parts, which describe all database objects.

For ODBC applications that use NonStop ODBC Server object names, you must duplicate those

names by using the logical ANSI names in the SQL/MX environment that match the names defined

in the NonStop ODBC Server environment. All metadata information returned by ODBC/MX for

those names will match the metadata information defined for NonStop ODBC Server.

NOTE: You do not need to duplicate names if the application does not rely on the NonStop

ODBC Server logical names. However, if you want to use long object names, use the CREATE

SQLMP ALIAS command in MXCI to add the long names to SQL/MX. The catalog and schema

names must exist before you create the alias.

ANSI Names

ANSI names (also called alias names) are logical names that map to physical Guardian names of

existing SQL/MP objects; they are defined by using the MXCI interface CREATE SQLMP ALIAS

command. ANSI is the default name type.

To migrate to SQL/MX, use MXCI to move the NonStop ODBC Server database object names to

the SQL/MX environment.

Name Mapping

NonStop ODBC Server uses customized catalogs to provide a three-part name mapping (logical

names) for all SQL objects stored in a user SQL catalog. User catalog customization is done through

the NOSCOM (or NOSUTIL) programs. An SQL/MP object name is not visible to the NonStop

ODBC Server environment if it has not been customized. NonStop ODBC Server provides a

three-part naming convention based on the Microsoft SQL Server implementation. The Owner

(Schema) represents a collection of objects created by one user in the given Database name

(catalog).

Within the ODBC/MX environment, you can add selected table names to the logical table names

by using an SQL/MX command. The logical name is available through the SQL/MX MXCI in

addition to client applications.

SQL/MX supports a three-part naming convention based on the ANSI SQL-92 standard. The catalog

name represents a collection of schemas, and a schema represents a collection of database object

names.

If the same names are required, you must add the corresponding alias names to tables used in

NonStop ODBC Server by using the database name as the catalog name, the owner name as the

schema name, and the object name as the SQL/MX object name. Object names can be defined

in the SQL/MX environment by using the CREATE SQLMP ALIAS command in MXCI.

NOTE: When you create an SQL/MP alias, the catalog and schema must exist. If they do not,

create them using MXCI before you create the alias.

Server: Duplicating NonStop ODBC Server Logical Database Object Names 57