MX 2.x)

ODBC/MX Client Overview

HP NonStop ODBC/MX Driver for Windows—527888-004

1-10

Traces

For information on migrating NonStop ODBC Server client applications to an

ODBC/MX environment, see the SQL/MX Comparison Guide for NonStop SQL/MP

Users.

Traces

You can trace activity for the ODBC Client.

Data collected:

•

Entry and exit calls from Microsoft ODBC driver manager to the ODBC/MX driver

•

Contents of the buffers, except password buffers

•

Activity between the ODBC/MX driver and the transport layer

For more information about client tracing, click the Help button on the Client Microsoft

Data Source Administrator.

For information about configuring client data source traces, see Tracing Client Data

Sources on page 3-3.

SQLStatistics Function This function does not support pattern value arguments for

table names, and returns index information for a specified

table name in the SQL/MX catalog.

If the index and table information is not in the SQL/MX

catalog, then it looks in the SQL/MP object (matching the

criteria) registered in the MP_PARTITIONS table (through

aliases) by looking up the catalog (where each table is

registered), then returns the index information for that

SQL/MP table.

SQLTables Function

When CatalogName is

SQL_ALL_CATALOGS

When SchemaName is

SQL_ALL_SCHEMAS

When TableType is

SQL_ALL_TABLE_TYPES

Returns all catalogs defined in the SQL/MX metadata.

Returns all schemas defined in the SQL/MX metadata.

Returns all object types supported by SQL/MX.

SQL Table Names

SQL Catalog and Schema

Names

The ODBC driver uses SQL_ATTR_METADATA_ID to

determine whether to upshift a table name. This applies for

catalog API to SQLTables, SQLPrimaryKey, and

SQLStatistics. This does not apply to SQLColumns.

Table 1-1. Release Considerations and Restrictions (page 3 of 3)