MX Release 3.2.1 (H06.26+, J06.15+)

See the MXCS online help that is available on NSM/web for detailed descriptions of the statistics

collected.

For information on configuring statistics collection, see “Configuring Statistics Collection” (page 40).

MXCS Features

MXCS supports the following features:

• Row size limit is increased to align with maximum block size 32768 for MX tables.

• A clustering key length up to 2048 bytes is allowed for range and hash partitioned MX tables.

• SQL/MX connectivity supports the extended NUMERIC precision data type. The precision of

this data type is extended up to 128 digits for signed and unsigned values. The extended

NUMERIC precision data type is used to hold temporary values while computing the result of

arithmetic expressions.

• Parameterized queries with BIGNUM data type.

Limitation of MXCS

The SQL/MX Release 2.x version of connectivity drivers are not compatible with the SQL/MX

Release 3.x version of the connectivity server. If you try to connect a SQL/MX Release 2.x version

of the connectivity driver to a SQL/MX Release 3.x version of the connectivity server, the behavior

is unpredictable. SQL/MX Release 3.0 base drivers are not compatible with SQL/MX Release 3.1

servers.

Unsupported NonStop ODBC Server Features

MXCS does not support the following NonStop ODBC Server features:

• TDS messages (for DBLib clients)

• T-SQL

• User catalog customization (supported in ANSI)

• Pass-through commands

• Named pipes and IPX/SPX network protocols

Migrating From a NonStop ODBC Server Environment

You must migrate your NonStop ODBC Server applications if you plan to take advantage of the

compiler and executor features of SQL/MX Release 3.x for your applications. By migrating your

applications, you also take advantage of the ODBC 3.5 compliant API driver. Like SQL/MX (BSR

X3.135-1992), ODBC/MX is based on the ISO/IEC 9075-3 standard and documented by Microsoft

in the ODBC 3.5 Programmer's Guide.

For more information on the necessary application and configuration modifications for migration

in both the server and the client environments, see “Migrating Applications from NonStop ODBC

Server” (page 56).

MXCS Features 17