ODBC/MX Driver for Windows Manual for SQL/MX Release 3.2.1 (H06.26+, J06.15+)
Table Of Contents
- HP NonStop ODBC/MX Driver for Windows
- Legal Notices
- Contents
- What’s New in This Manual
- About This Manual
- 1 ODBC/MX Client Overview
- 2 Installation of the ODBC/MX Client
- 3 Configuring Client Data Sources on Windows
- Accessing the Microsoft ODBC Data Source Administrator from a Client Workstation
- Adding New Client Data Sources
- Reconfiguring Client Data Sources
- Configuring Client Data Sources using Connection String
- Configuring Client Data Sources for Update Operations
- Configuring Driver for IPV6
- Removing Client Data Sources
- Tracing Client Data Sources
- 4 Module File Caching (MFC)
- 5 ODBC/MX Conformance
- ODBC API Functions
- SQL Conformance Level
- SQL Scalar Functions
- ODBC Data Types
- Unsigned Data Types
- Partial Date/Time Values
- SQL/MP Data Types and ODBC/MX Equivalents
- Microsoft Escape Clauses
- Stored Procedures
- Transactions and Cursor Behavior with Multiple Statements
- Timestamp Values with Fraction
- SQL Interval Insertion Property
- SQL Datetime Retrieval Property
- 6 ODBC/MX Messages
- Glossary
- Index
ODBC/MX Client Overview
HP NonStop ODBC/MX Driver for Windows—691126-002
1-8
Release Considerations and Restrictions
Release Considerations and Restrictions
Table 1-1. Release Considerations and Restrictions (page1of3)
ODBC driver manager ODBC/MX requires the Microsoft ODBC 3.5.1 (or later) driver
manager. If you do not already have the 3.5.1 driver manager,
ODBC/MX installs it for you.
ODBC/MX client software An ODBC/MX client can be installed in the same workstation
as other ODBC client software.
R 2.3.x version of Windows ODBC/MX Driver can co-exist
with R3.x version of ODBC/MX Client Driver.
Catalog and schema An ODBC client application can set the catalog and schema
for an ODBC client data source by using the ODBC/MX Setup
window in the Microsoft ODBC Data Source Administrator.
If an ODBC client does not set the catalog and schema for an
ODBC client data source, the MXCS server defaults to
NONSTOP_SYSTEM_NSK and
PUBLIC_ACCESS_SCHEMA, respectively.
Note:
By default, catalog and schema names are case
insensitive and follow SQL/MX rules. Case sensitive
catalog and schema names can be specified within
quotes.
catalog and schema names that are defined by default
are not recognized by MXCS for client data sources
because they are not defined through the Microsoft
ODBC Data Source Administrator. You must either define
the catalog and schema names using the Microsoft
ODBC Data Source Administrator, or use the fully
qualified object name.
SQL_QUERY_TIMEOUT
Option
An ODBC application can call SQLSetStmtOption with the
SQL_QUERY_TIMEOUT option to specify the number of
seconds to wait for a query to execute. The
SQL_QUERY_TIMEOUT option protects the MXCS server
and ODBC client from long running queries. If a query
exceeds the specified time before the data source returns the
result set, the ODBC/MX driver returns HYT00 (Timeout
expired) to the ODBC client.