Connect ODBC 7.1.6 Windows
- Last Updated: May 8, 2026
- 35 minute read
- OpenAccess SDK
- Documentation
README
Progress(R) DataDirect(R)
DataDirect Connect(R) for ODBC
DataDirect Connect XE (Extended Edition) for ODBC
DataDirect Connect64(R) for ODBC
DataDirect Connect64 XE (Extended Edition) for ODBC
Windows Platforms
Release 7.1.6
February 2026
***********************************************************************
Copyright (C) 2026 Progress Software Corporation and/or its
subsidiaries or affiliates. All Rights Reserved.
***********************************************************************
This README file contains information for Progress(R) DataDirect
Connect(R) Series for ODBC, which includes the following products:
* DataDirect Connect for ODBC
* DataDirect Connect64 for ODBC
* DataDirect Connect XE (Extended Edition) for ODBC
* DataDirect Connect64 XE for ODBC
This README file contains information not included in the DATADIRECT
CONNECT(R) SERIES FOR ODBC documentation.
IMPORTANT: You must have the Microsoft Data Access Components (MDAC)
installed to use this product.
* For 32-bit Windows systems, version 2.6 or higher is required.
* For 64-bit Windows systems, version 2.8 or higher is required.
Depending on the version of your Windows operating system, these
components may already be installed. You can download a utility that
determines whether MDAC is installed and its version from the following
Microsoft site:
http://msdn.microsoft.com/en-us/data/aa937730.aspx
You can also download MDAC from the same site.
CONTENTS
Post-GA Product Announcements
Installation Directory
Data Source and Platform Support
Changes Since Service Pack 6 GA
Changes for Service Pack 6 GA
Changes for Service Pack 5 GA
Changes for Service Pack 4 GA
Changes Since Service Pack 3
Changes for Service Pack 3 GA
Changes Since Service Pack 2 GA
Changes for Service Pack 2 GA
Changes Since Service Pack 1 GA
Changes for Service Pack 1
Release 7.1.0 Features
Available ODBC Drivers
Disk Space Requirements
Driver WorkAround Options
Notes, Known Problems, and Restrictions
Documentation
Installed Files for 32-bit Drivers
Installed Files for 64-bit Drivers
Post-GA Product Announcements
The readme files will no longer be updated with product announcements and new
features after the General Availability (GA) of the product. For the latest
updates and enhancements, please refer to the release notes
(https://www.progress.com/datadirect-connectors/whats-new).
Installation Directory
* The default installation directory for DataDirect Connect for ODBC
and DataDirect Connect XE for ODBC is:
C:\Program Files\Progress\DataDirect\Connect_for_ODBC_71
* The default installation directory for DataDirect Connect64 for ODBC
and DataDirect Connect64 XE for ODBC is:
C:\Program Files\Progress\DataDirect\Connect64_for_ODBC_71
Data Source and Platform Support
For the latest data source and platform support information, refer to the
Product Compatibility Guide:
https://docs.progress.com/bundle/datadirect-product-compatibility/resource/
datadirect-product-compatibility.pdf
Changes Since Service Pack 6 GA
SSL Enhancement (1.1.1t)
------------------------
The default version of the OpenSSL library has been upgraded to version
1.1.1t, which fixes the following security vulnerabilities:
* X.400 address type confusion in X.509 GeneralName (CVE-2023-0286)
* Use-after-free following BIO_new_NDEF (CVE-2023-0215)
* Double free after calling PEM_read_bio_ex (CVE-2022-4450)
* Timing Oracle in RSA Decryption (CVE-2022-4304)
This upgrade is available in build 07.16.0184 of the following OpenSSL library
files: ivtls27.dll (32-bit) and ddtls27.dll (64-bit).
Version 1.1.1t also addresses vulnerabilities resolved by earlier versions
of the library.
For more information on OpenSSL vulnerabilities resolved by this upgrade,
refer to the corresponding OpenSSL announcements at:
https://www.openssl.org/news/vulnerabilities-1.1.1.html
End of Support for OpenSSL 1.0.2
--------------------------------
The product no longer includes version 1.0.2 of the OpenSSL library.
The library has reached the end of its product life cycle and is not
receiving security updates anymore. Note that continuing to use the
library could potentially expose you to security vulnerabilities.
Note: As a result of this change, when installing a new version of the
driver, the installer program will automatically remove version 1.0.2
of the library from the install directory.
SSL Enhancement (1.1.1n)
------------------------
Note: OpenSSL library 1.1.1n has been replaced with version 1.1.1t. In
addition to fixing multiple new vulnerabilities, version 1.1.1t also
addresses the vulnerabilities resolved by version 1.1.1n.
The default version of the OpenSSL library has been upgraded to version
1.1.1n, which fixes the following security vulnerabilities:
* Infinite loop in BN_mod_sqrt() reachable when parsing certificates
(CVE-2022-0778)
* BN_mod_exp may produce incorrect results on MIPS (CVE-2021-4160)
This upgrade is available in build 07.16.0069 of the following OpenSSL library
files: ivtls27.dll (32-bit) and ddtls27.dll (64-bit).
SSL Enhancement (1.1.1l)
------------------------
Note: OpenSSL library 1.1.1l has been replaced with version 1.1.1n. In
addition to fixing multiple new vulnerabilities, version 1.1.1n also
addresses the vulnerabilities resolved by version 1.1.1l.
The default version of the OpenSSL library has been upgraded to version
1.1.1l, which fixes the following security vulnerabilities:
* SM2 Decryption Buffer Overflow (CVE-2021-3711)
* Read buffer overruns processing ASN.1 strings (CVE-2021-3712)
This upgrade is available in build 07.16.0061 of the following OpenSSL library
files: ivtls27.dll (32-bit) and ddtls27.dll (64-bit).
SSL Enhancement (1.1.1k)
------------------------
Note: OpenSSL library 1.1.1k has been replaced with version 1.1.1l. In
addition to fixing multiple new vulnerabilities, version 1.1.1l also
addresses the vulnerabilities resolved by version 1.1.1k.
The default version of the OpenSSL library has been upgraded to version
1.1.1k, which fixes the following security vulnerabilities:
* CA certificate check bypass with X509_V_FLAG_X509_STRICT (CVE-2021-3450)
* NULL pointer deref in signature_algorithms processing (CVE-2021-3449)
* Null pointer deref in X509_issuer_and_serial_hash() (CVE-2021-23841)
* Integer overflow in CipherUpdate (CVE-2021-23840)
This upgrade is available in build 07.16.0056 of the following OpenSSL library
file: ivtls27.dll (32-bit) and ddtls27.dll (64-bit).
Documentation
-------------
Any product package made available after February 9, 2021 will not include the
HTML help system or user's guide PDF. The Progress DataDirect Connect Series for
ODBC documentation set is available via product and data source tiles from the
Progress Information Hub:
https://docs.progress.com
While the product packages will not include these documentation items, the
installation Help directory will provide an HTML redirect for direct access
to the HTML help.
SSL Enhancement (1.1.1i)
------------------------
Note: OpenSSL library 1.1.1i has been replaced with version 1.1.1k. In
addition to fixing multiple new vulnerabilities, version 1.1.1k also
addresses the vulnerabilities resolved by version 1.1.1i.
The default version of the OpenSSL library has been upgraded to version 1.1.1i,
which fixes the following security vulnerabilities: Incorrect behavior of the
GENERAL_NAME_cmp function (CVE-2020-1971).
This upgrade is available in build 07.16.0045 of the following OpenSSL library
files: ivtls27.dll (32-bit) and ddtls27.dll (64-bit).
SSL Enhancement (1.1.1g)
------------------------
Note: OpenSSL library 1.1.1g has been replaced with version 1.1.1k. In
addition to fixing multiple new vulnerabilities, version 1.1.1k also
addresses the vulnerabilities resolved by version 1.1.1g.
The default version of the OpenSSL library has been upgraded to version 1.1.1g,
which fixes the following security vulnerabilities:
* Segmentation fault in SSL_check_chain (CVE-2020-1967)
* rsaz_512_sqr overflow bug on x86_64 (CVE-2019-1551)
Timestamp Logging in Packet Logs
--------------------------------
The drivers using base version B0548 and later have been enhanced to include
timestamp in the internal packet logs by default. If you want to disable the
timestamp logging in packet logs, set PacketLoggingOptions=1. The internal
packet logging is not enabled by default. To enable it, set
EnablePacketLogging=1.
SSL Enhancement (1.1.1d)
------------------------
Note: OpenSSL library 1.1.1d has been replaced with version 1.1.1g. In addition
to fixing multiple new vulnerabilities, version 1.1.1g also addresses the
vulnerabilities resolved by version 1.1.1d.
This upgrade is available in the 1.1.1 version of the OpenSSL library files,
ivtls27.dll (32-bit) and ddtls27.dll (64-bit).
(For SSL-enabled drivers) AllowedOpenSSLVersions
------------------------------------------------
Determines which version of the OpenSSL library file the driver uses for data
encryption when multiple versions are installed with the product. For example,
when specifying a value of 1.1.1 (AllowedOpenSSLVersions=1.1.1), the driver
uses the 1.1.1 version of the library stored in the /lib subdirectory. Refer to
the user's guide for more information.
DB2 Wire Protocol Driver
------------------------
* The driver has been enhanced to support Select queries with parameterized
arrays.
Greenplum Wire Protocol
-----------------------
* The driver has been enhanced with the new Batch Mechanism (BatchMechanism)
connection option, which specifies the preferred mechanism for executing
batch insert operations. By setting Batch Mechanism to 2 (MultiRowInsert) or
3 (Copy), the driver can achieve substantial performance gains when
performing batch inserts. The default setting is BatchMechanism=1
(SingleRowInsert).
* The driver has been enhanced to support the following data types: Citext,
Float, and Tinyint.
* A Power BI connector is now included with the product package. You can use
this connector to access your Greenplum data with Power BI. Refer to the
user's guide for details.
Impala Wire Protocol
--------------------
* The Batch Mechanism connection option has been added to the driver. When
BatchMechanism is set to 2 (MultiRowInsert), the driver executes a single
insert for all the rows contained in a parameter array. MultiRowInsert is
the default setting and provides substantial performance gains when
performing batch inserts. Refer to the user's guide for
details.
* The driver has been enhanced to support SSL encryption, which can be
configured using the following new connection options:
- Crypto Protocol Version - CrypoLibName
- Encryption Method - Host Name in Certificate
- Key Password - Key Store
- Key Store Password - SSLLibName
- Trust Store - Trust Store Password
- Validate Server Certificate
SSL support was formally certified against driver version 07.16.0317
(B0386, U0249). Refer to the user's guide for additional information.
MySQL Wire Protocol Driver
--------------------------
* The driver has been enhanced to support the sha256_password and
caching_sha2_password authentication plugins.
Oracle Wire Protocol Driver
---------------------------
* The maximum supported length of identifiers has been increased to 128 bytes
when connecting to Oracle 12c R2 (12.2) databases. This change has been
implemented to reflect the new maximum length supported by the server.
PostgreSQL Wire Protocol
------------------------
* The driver has been enhanced to support the scram-sha-256-plus authentication
method, which uses channel binding for establishing a secure connection with
PostgreSQL (v11.0 and higher).
* The driver has been enhanced to support the following data types: Citext,
Float, and Tinyint.
* The driver has been enhanced with the new Batch Mechanism (BatchMechanism)
connection option, which specifies the preferred mechanism for executing
batch insert operations. By setting Batch Mechanism to 2 (MultiRowInsert) or
3 (Copy), the driver can achieve substantial performance gains when
performing batch inserts. The default setting is BatchMechanism=1
(SingleRowInsert).
* A Power BI connector is now included with the product package. You can use
this connector to access your PostgreSQL data with Power BI. Refer to the
user's guide for details.
* For PostgreSQL 9.0 and later, the driver behavior has been updated to support
executing multiple prepared statements in a single query that contain inserts
for BYTEA values. However, for versions earlier than PostgreSQL 9.0, this
functionality is not supported and the driver returns an error.
* The driver has been enhanced to support Select queries with parameterized
arrays.
* The driver has been enhanced to support md5 and scram-sha-256 authentication
methods.
* The driver has been enhanced to support materialized views and
foreign tables.
Progress OpenEdge Wire Protocol Driver
--------------------------------------
* The driver has been enhanced to support the SQLCancel function for SELECT
statements with OpenEdge V12.4 and higher. If a SELECT statement is cancelled
during the first or a subsequent fetch operation, the driver returns a
"query aborted" exception. This method can be used by a thread to cancel a
statement that is being executed by another thread. One or more statements may
be cancelled if the method is called on a statement object that is executing
multiple statements simultaneously and the driver may not return expected
results. The driver supports this function for ODBC 3.x applications only.
SQL Server Wire Protocol
------------------------
* The 7.1 version of the driver no longer supports the curl library.
As a result, the following functionality will no longer be supported:
Azure Active Directory Authentication.
* The driver is enhanced to support Azure Active Directory authentication
(Azure AD). Azure AD authentication is an alternative to SQL Server
Authentication for Azure SQL Database that allows you to centrally manage
identities of database users. To enable Azure AD authentication, specify the
new 13 - Active Directory Password value for the Authentication Method
connection option (AuthenticationMethod=13). In addition, specify the
respective values in the connection string or data source definition for the
Host Name In Certificate, Trust Store, Validate Server Certificate, User Name
and Password connection options. Refer to "Configuring Azure Active Directory
Authentication" in the user's guide for more information.
* The driver has been enhanced to support Always On Availability Groups.
Introduced in SQL Server 2012, Always On Availability Groups is a
replica-database environment that provides a high-level of data availability,
protection, and recovery. To support this enhancement, the following updates
have been made to the driver:
- The Host Name option has been updated to support the virtual network
name (VNN) of the availability group listener as a valid value. To connect
to an Always On Availability group, you must specify the VNN with this
option.
- The new Application Intent option allows you to control whether the driver
requests read-only routing, thereby improving efficiency by reducing the
workload on read-write nodes.
- The new MultiSubnetFailover option allows the driver to attempt parallel
connections to all the IP addresses associated with an availability group
when the primary listener is unavailable. This offers improved response
time over traditional failover, which attempts connections to alternate
servers one at a time.
Refer to the user's guide for details.
Sybase Wire Protocol
--------------------
* The driver has been enhanced to support Sybase Extended Password Encryption
and Sybase Extended Plus Encrypted Password, which use an asymmetrical key
type. This provides stronger password encryption for the secure transmission
of public key passwords over networks.
* The driver has been enhanced to support binary and varbinary data types when
using the bulk load protocol.
Driver for Teradata
-------------------
* The driver has been enhanced to support the Number data type. Refer to the
user's guide for additional information.
Text Driver
-----------
* The Connect64 (64-bit) version of the Text driver is now generally available.
This new driver provides 64-bit support for the features and functionality
offered by the earlier DataDirect Connect (32-bit) version of the driver.
Notes:
- The Connect64 Text driver uses a driver-specific installer, instead of
the Connect Series installer. Both installers are available on the
Progress website.
- The control numbers available in the new control number format
(8.0 control numbers) must be used for installing the Connect64 Text driver,
instead of those available in the old format (7.1 control numbers).
XML Driver
----------
* The driver has been enhanced to support Microsoft XML parser (MSXML) 6.0.
Note that MSXML 6.0 (msxml6.dll) must be installed on your machine for the
driver to function correctly.
Refer to the fixes.txt file in the product installation directory for a list of
changes by build number.
Changes for Service Pack 6 GA
Driver for Apache Hive
----------------------
* The driver has been enhanced to support row-level inserts when connected
to Hive 0.14 or higher.
* The Batch Mechanism connection option has been added to the driver. By
setting Batch Mechanism to 2 (MultiRowInsert), you enable the driver to use a
parameterized multi-row insert statement to execute batch inserts.
MultiRowInsert is the default setting and provides substantial performance
gains when performing batch inserts.
* The Authentication Method connection option has been refreshed with a new
valid value for enabling Kerberos Authentication. To use Kerberos
authentication with the driver, set AuthenticationMethod=4.
* The new CryptoLibName and SSLLibName connection options allow you to
designate the OpenSSL libraries used when SSL is enabled.
* The driver has been enhanced to support SSL encryption, which can be
configured using the following new connection options:
- Crypto Protocol Version - Key Store Password
- Encryption Method - Trust Store
- Host Name in Certificate - Trust Store Password
- Key Password - Validate Server Certificate
- Key Store
* The Array Size configuration option has been refreshed to allow specifying
the number of cells retrieved instead of rows. By determining the fetch size
based on the number of cells, the driver can avoid out of memory errors when
fetching from tables containing a large number of columns.
DB2 Wire Protocol Driver
------------------------
* The new CryptoLibName and SSLLibName connection options allow you to
designate the OpenSSL libraries used when SSL is enabled.
* The new Min Long Varchar Size connection option allows you to fetch
SQL_LONGVARCHAR columns whose size is smaller than the minimum
imposed by some third-party applications.
* The new Varchar Threshold connection option allows you to fetch columns
that would otherwise exceed the upper limit of the SQL_VARCHAR type for some
third-party applications.
Greenplum Wire Protocol
-----------------------
* The new CryptoLibName and SSLLibName connection options allow you to
designate the OpenSSL libraries used when SSL is enabled.
* Support for Kerberos Authentication, which can be configured using the
following new connection options:
-Authentication Method
-GSS Client Name
-Service Principal Name
-User Name
Impala Wire Protocol
--------------------
* The Authentication Method connection option has been refreshed with a new
valid value for enabling Kerberos Authentication. To use Kerberos
authentication with the driver, set AuthenticationMethod=4.
* Support for Kerberos Authentication, which can be configured using the
following new connection options:
-Authentication Method
-GSS Client Library
-Proxy User
-Service Principal Name
* Certified with Apache Sentry for Impala 1.1 and higher. Sentry enables
administrators to control access to data and metadata stored on an Hadoop
cluster by defining user roles and permissions. For more information, refer
to the DATADIRECT CONNECT FOR ODBC SERIES USER'S GUIDE.
* The driver has been enhanced to support the Char, Decimal, and Varchar data
types when connected to Impala 2.0 and higher.
* The Array Size configuration option has been refreshed to allow specifying
the number of cells retrieved instead of rows. By determining the fetch size
based on the number of cells, the driver can avoid out of memory errors when
fetching from tables containing a large number of columns.
MySQL Wire Protocol Driver
--------------------------
* The new CryptoLibName and SSLLibName connection options allow you to
designate the OpenSSL libraries used when SSL is enabled.
Oracle Wire Protocol Driver
---------------------------
* The new CryptoLibName and SSLLibName connection options allow you to
designate the OpenSSL libraries used when SSL is enabled.
PostgreSQL Wire Protocol
------------------------
* Support for Kerberos Authentication, which can be configured using the
following new connection options:
-Authentication Method
-GSS Client Name
-Service Principal Name
-User Name
Progress OpenEdge Wire Protocol Driver
--------------------------------------
* The new CryptoLibName and SSLLibName connection options allow you to
designate the OpenSSL libraries used when SSL is enabled.
SQL Server Wire Protocol
------------------------
* The new CryptoLibName and SSLLibName connection options allow you to
designate the OpenSSL libraries used when SSL is enabled.
Sybase Wire Protocol
--------------------
* The new CryptoLibName and SSLLibName connection options allow you to
designate the OpenSSL libraries used when SSL is enabled.
For more information about these features, refer to the DATADIRECT CONNECT
FOR ODBC SERIES USER'S GUIDE.
Changes for Service Pack 5 GA
Driver for Apache Hive
----------------------
* Certified with Apache Hive Sentry, which enables HiveServer2 administrators
to enforce role-based authorization for Apache Hadoop clusters.
* The driver has been enhanced to support the Char data type
when connected to Hive 0.13 and higher.
* The driver has been enhanced to support the Decimal data type
when connected to Hive 0.11 and higher.
* The driver has been enhanced to support the Date and Varchar data types
in Hive 0.12 and higher.
DB2 Wire Protocol Driver
------------------------
* The new Crypto Protocol Version connection option allows you to specify
the cryptographic protocols used when SSL is enabled. This option can be
used to avoid vulnerabilities associated with SSLv3 and SSLv2, including
the POODLE vulnerability.
Greenplum Wire Protocol Driver
------------------------------
* The new Crypto Protocol Version connection option allows you to specify
the cryptographic protocols used when SSL is enabled. This option can be
used to avoid vulnerabilities associated with SSLv3 and SSLv2, including
the POODLE vulnerability.
* The new Unbounded Numeric Precision connection option allows you to
define the precision for unbounded NUMERIC columns when described
within the column, parameter, result set, or table metadata.
* The new Unbounded Numeric Scale connection option allows you to
define the scale for unbounded NUMERIC columns described within
the column, parameter, result set, or table metadata.
MySQL Wire Protocol Driver
--------------------------
* The new Crypto Protocol Version connection option allows you to specify
the cryptographic protocols used when SSL is enabled. This option can be
used to avoid vulnerabilities associated with SSLv3 and SSLv2, including
the POODLE vulnerability.
Oracle Wire Protocol Driver
---------------------------
* The new Crypto Protocol Version connection option allows you to specify
the cryptographic protocols used when SSL is enabled. This option can be
used to avoid vulnerabilities associated with SSLv3 and SSLv2, including
the POODLE vulnerability.
PostgreSQL Wire Protocol Driver
-------------------------------
* The new Crypto Protocol Version connection option allows you to specify
the cryptographic protocols used when SSL is enabled. This option can be
used to avoid vulnerabilities associated with SSLv3 and SSLv2, including
the POODLE vulnerability.
* The new Unbounded Numeric Precision connection option allows you to
define the precision for unbounded NUMERIC columns when described
within the column, parameter, result set, or table metadata.
* The new Unbounded Numeric Scale connection option allows you to
define the scale for unbounded NUMERIC columns described within
the column, parameter, result set, or table metadata.
Progress OpenEdge Wire Protocol Driver
--------------------------------------
* The new Crypto Protocol Version connection option allows you to specify
the cryptographic protocols used when SSL is enabled. This option can be
used to avoid vulnerabilities associated with SSLv3 and SSLv2, including
the POODLE vulnerability.
SQL Server Wire Protocol Driver
-------------------------------
* The driver has been enhanced to support NTLMv2 authentication, which can be
configured using the Authentication Method connection option.
* The new Crypto Protocol Version connection option allows you to specify
the cryptographic protocols used when SSL is enabled. This option can be
used to avoid vulnerabilities associated with SSLv3 and SSLv2, including
the POODLE vulnerability.
Sybase Wire Protocol Driver
---------------------------
* The new Crypto Protocol Version connection option allows you to specify
the cryptographic protocols used when SSL is enabled. This option can be
used to avoid vulnerabilities associated with SSLv3 and SSLv2, including
the POODLE vulnerability.
For more information about these features, refer to the DATADIRECT CONNECT FOR
ODBC SERIES USER'S GUIDE.
Changes for Service Pack 4 GA
No features introduced
Changes Since Service Pack 3 GA
Driver for Apache Hive
----------------------
* The new TCP Keep Alive connection option allows you to
use TCP Keep Alive to maintain idle TCP connections.
DB2 Driver
----------
* The new TCP Keep Alive connection option allows you to
use TCP Keep Alive to maintain idle TCP connections.
Greenplum Wire Protocol Driver
------------------------------
* The new TCP Keep Alive connection option allows you to
use TCP Keep Alive to maintain idle TCP connections.
MySQL Wire Protocol
-------------------
* The new TCP Keep Alive connection option allows you to
use TCP Keep Alive to maintain idle TCP connections.
Oracle Wire Protocol Driver
---------------------------
* The new TCP Keep Alive connection option allows you to
use TCP Keep Alive to maintain idle TCP connections.
PostgreSQL Wire Protocol Driver
-------------------------------
* The new TCP Keep Alive connection option allows you to
use TCP Keep Alive to maintain idle TCP connections.
Progress OpenEdge Wire Protocol Driver
--------------------------------------
* The new TCP Keep Alive connection option allows you to
use TCP Keep Alive to maintain idle TCP connections.
SQL Server Wire Protocol
------------------------
* The new TCP Keep Alive connection option allows you to
use TCP Keep Alive to maintain idle TCP connections.
Sybase Wire Protocol Driver
---------------------------
* The new TCP Keep Alive connection option allows you to
use TCP Keep Alive to maintain idle TCP connections.
For more information about these features, refer to the
DATADIRECT CONNECT FOR ODBC SERIES USER'S GUIDE.
Changes for Service Pack 3 GA
Driver for Apache Hive
----------------------
* The Use Native Catalog Functions connection option allows you to use native
catalog functions to retrieve information returned by SQLTables, SQLColumns,
and SQLStatistics catalog functions.
* Support for Kerberos Authentication, which can be configured using the
following connection options:
-Authentication Method specifies the method the driver uses to authenticate
the user to the server when a connection is established.
-GSS Client Library specifies the GSS client library that the driver uses to
communicate with the Key Distribution Center (KDC).
-Proxy User Specifies the UserID used for HiveServer2 impersonation and
HiveServer2 Trusted Impersonation.
-Service Principal Name specifies the service principal name to be used by
driver for Kerberos authentication.
For more information about these features, refer to the
DATADIRECT CONNECT FOR ODBC SERIES USER'S GUIDE.
Changes Since Service Pack 2 GA
Greenplum Driver
----------------
* SSL support for Greenplum 4.2, incorporating nine additional connection
options.
Oracle Wire Protocol Driver
---------------------------
* Modified to support all Oracle 11gR2 Kerberos
encryption algorithms.
PostgreSQL Driver
-----------------
* The Encryption Method connection option now supports Request SSL
functionality. When Request SSL is enabled, login requests and data are
encrypted if the server is configured for SSL. If the server is not
configured for SSL, an unencrypted connection is established.
For more information about these features, refer to the
DATADIRECT CONNECT FOR ODBC SERIES USER'S GUIDE.
Changes for Service Pack 2 GA
New Driver
----------
* DataDirect Connect XE for ODBC Impala Wire Protocol driver
- Certified with Cloudera Impala database server and formally
certified with the following file formats and storage handlers:
- File Formats:
- Parquet
- Text File
- Storage Handlers
- HBase
- Returns result set metadata for parameterized statements
that have been prepared but not yet executed.
- Supports parameter arrays, processing the arrays as a series of
executions, one execution for each row in the array.
- Provides a connection option that allows you to configure
the driver to report that it supports transactions, although
Hive does not support transactions. This provides a workaround
for applications that do not operate with a driver that reports
transactions are not supported.
- Provides a connection option that allows you to set a default limit for
the number of rows returned when an ORDER BY clause is submitted. This
provides a workaround for applications that are not compatible with
Impala's requirement that ORDER BY clauses limit the number of rows returned.
- The driver provides support for the following standard SQL
functionality:
- Create Index and Create Table
- Insert, Update, and Delete
- Drop Index and Drop Table
For more information about these features, refer to the
DATADIRECT CONNECT FOR ODBC SERIES USER'S GUIDE.
Changes Since Service Pack 1 GA
Driver for Apache Hive(TM)
--------------------------
The Driver for Apache Hive Version 7.1.1 has been refreshed and
contains the following changes since the GA release:
* The String Describe Type connection option now allows you to describe
string columns as SQL_WLONGVARCHAR or SQL_WVARCHAR.
For more information about these features, refer to the
DATADIRECT CONNECT FOR ODBC SERIES USER'S GUIDE.
Changes for Service Pack 1 GA
Driver for Apache Hive(TM)
--------------------------
The Driver for Apache Hive Version 7.1.0 has been refreshed and
contains the following changes since the GA release:
* Added support for HiveServer2.
* The Password connection option is now a required field
on the "Logon to Apache Hive" dialog box for a connection
or test connection to HiveServer2.
* The User Name connection option is now a required field
on the "Logon to Apache Hive" dialog box for a connection
or test connection to HiveServer2.
* When connected to HiveServer2, simultaneous connections per port
are supported.
* The new Wire Protocol Version connection option specifies the
version of the Hive Server to which the driver will connect.
NOTE: If the value set for Wire Protocol Version does not match the
version of the Hive server to which you are connecting, the connection
fails with a login timeout error, if Login Timeout is enabled.
For example, a login timeout error is returned if the driver attempts
to connect to a HiveServer1 data source when WireProtocolVersion=2.
For more information about these features, refer to the
DATADIRECT CONNECT FOR ODBC SERIES USER'S GUIDE.
Release 7.1.0 Features
New Driver
----------
* DataDirect Connect XE for ODBC for Apache Hive(TM) Wire Protocol driver
- Supported with the following Apache Hive versions:
- Amazon Elastic MapReduce (Amazon EMR)
- Apache Hadoop Hive
- Cloudera Distribution Including Apache Hadoop (CDH)
- MapR Distribution for Apache Hadoop
- Returns result set metadata for parameterized statements
that have been prepared but not yet executed.
- Supports parameter arrays, processing the arrays as a series of
executions, one execution for each row in the array.
- Provides a connection option that allows you to configure
the driver to report that it supports transactions, although
Hive does not support transactions. This provides a workaround
for applications that do not operate with a driver that reports
transactions are not supported.
- The driver provides support for the following standard SQL
functionality:
- Create Index, Create Table, and Create View
- Insert
- Drop Index, Drop Table, and Drop View
Oracle Wire Protocol Driver Enhancements
----------------------------------------
* Support for Oracle Advanced Security (OAS), which can be configured
using the following connection options:
- DataIntegrityLevel sets the level of OAS data integrity
used for data sent between the driver and database server.
- DataIntegrityTypes specifies one or multiple algorithms to protect against
attacks that intercept and modify data being transmitted between the client
and server when OAS data integrity is enabled using the DataIntegrityLevel
property.
- EncryptionLevel determines whether data is encrypted and decrypted when
transmitted over the network between the driver and database server using
OAS encryption.
- EncryptionTypes specifies one or multiple algorithms to use if OAS encryption
is enabled using the EncryptionLevel property.
Salesforce Driver Enhancements
------------------------------
* The RefreshSchema option determines whether the driver automatically
refreshes the remote object mapping and other information contained
in a remote schema the first time a user connects to the specified
embedded database.
* The KeywordConflictSuffix keyword=value pair specifies a string of up to
five alphanumeric characters that the driver appends to any object or
field name that conflicts with a SQL engine keyword. For example,
if you specify KeywordConflictSuffix=TAB, then the driver maps the
Case object in Salesforce to CASETAB.
For more information about these features, refer to the DATADIRECT CONNECT
FOR ODBC SERIES USER'S GUIDE.
Available ODBC Drivers
Database drivers are continually being added to each operating
environment. For the latest information about the specific drivers
available for your platform, refer to the Progress DataDirect database
support matrix Web page.
Disk Space Requirements
32-bit drivers: The following available disk space requirements assume a
full installation of all 32-bit drivers and options.
* DataDirect Connect for ODBC Drivers: 55 MB
* DataDirect Connect XE for ODBC Drivers: 75 MB
64-bit drivers: The following available disk space requirements assume a
full installation of all 64-bit drivers and options.
* DataDirect Connect64 for ODBC Drivers: 55 MB
* DataDirect Connect64 XE for ODBC Drivers: 75 MB
Driver WorkAround Options
Progress DataDirect has included non-standard connection options
(workarounds) for the drivers that enable you to take full advantage of
packaged ODBC-enabled applications requiring non-standard or extended
behavior.
Refer to the chapter "WorkAround Options" in the DATADIRECT CONNECT
SERIES FOR ODBC REFERENCE for a description of these options.
Notes, Known Problems, and Restrictions
The following are notes, known problems, or restrictions with
Release 7.1.6 of the DataDirect Connect Series for ODBC drivers.
PostgreSQL: Batch Mechanism Option
----------------------------------
GUI Name:
Batch Mechanism
Attribute:
BatchMechanism (BM)
Purpose:
Determines the mechanism that is used to execute batch operations.
Valid Values:
1 | 2 | 3
Behavior:
If set to 1 (SingleRowInsert), the driver executes an insert statement for each
row contained in a parameter array. Specify this value if you are experiencing
out-of-memory errors when performing batch inserts.
If set to 2 (MultiRowInsert), the driver attempts to execute a single insert
statement for all the rows contained in a parameter array. If the size of the
insert statement exceeds the available buffer memory of the driver, the driver
executes multiple statements. Specify this value for substantial performance
gains over 1 (SingleRowInsert) when performing batch inserts.
If set to 3 (Copy), the driver uses the PostgreSQL COPY command to insert rows
into the target table. Specify this value for substantial performance gains
over 1 (SingleRowInsert) when performing batch inserts.
Notes:
* Batch Mechanism determines the mechanism used to perform batch inserts only.
For update and delete batch operations, the driver uses the native batch
mechanism to handle the request.
* When BatchMechanism=3, substantial performance gains can be made. However,
the following limitations apply:
- Individual update counts are not returned. However, the total number of
inserted rows are returned the execution of a batch operation.
- The entire batch insert is ATOMIC. If any issues are encountered, the
entire operation fails and no rows are inserted.
Default:
2 (MultiRowInsert)
GUI Tab:
Advanced
Driver for IBM DB2 - Default Value of XMLDescribeType Attribute
---------------------------------------------------------------
The difference in default value of XMLDescribeType attribute between
Unix/Linux and Windows platforms is a known issue. It will be resolved
in the 8.0 version of the driver.
Workaround: In the odbc.ini file, set the XMLDescribeType attribute to
the required value in the data source definition.
Power BI Connectors
-------------------
Branding for Power BI connectors is not currently supported.
DashDB Constraints for Tables
-----------------------------
By default, dashDB does not enforce constraints for tables. As a result, dashDB
will not enforce uniqueness on the new tables, and therefore, incorrect or
unexpected results can occur if table data violates the not-enforced
constraint. If you want to enforce uniqueness, specify the ENFORCED parameter
when creating or altering unique or referential constraints, such as primary
keys and foreign keys.
Disabling Diffie-Hellman Cipher Suites
--------------------------------------
If your database has not been fixed to address the Logjam vulnerability, you
can still use the most recent version of the OpenSSL Library by disabling the
Diffie-Hellman cipher suites. To disable the Diffie-Hellman cipher suites,
specify the following value for the undocumented CipherList connection option:
CipherList=DEFAULT:-DH
If you have already specified a value for CipherList, add the following to the
existing value:
:-DH
The option-value pair for undocumented options can be specified in the
connection string or the Extended Options field of the GUI. For
details, refer to "Configuring and Connecting to Data Sources" in the
individual driver chapters of the DATADIRECT CONNECT SERIES FOR ODBC
USER'S GUIDE.
126 Error When Modifying Data Sources on Windows 10
---------------------------------------------------
You may receive a 126 error when adding or configuring a data source stored
on a network location. This is caused by the settings of the User Account
Control (UAC) security feature on Windows 10. To work around this issue:
Important: Implementing this fix disables security safeguards that are designed
to protect your machine. Before starting, refer to the following Microsoft
documentation for potential risks associated with disabling the UAC feature:
http://windows.microsoft.com/en-us/
windows/what-are-user-account-control-settings
1. From the Start menu, type regedit in the search field; then, select regedit
from the results list. The Registry Editor window opens.
2. Navigate to the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
3. Right click on the subkey; then, select New > DWORD Value.
4. Rename the new value EnableLinkedConnections.
5. Right-click EnableLinkedConnections, and then click Modify. The Edit DWORD
Value window opens.
6. In the Value data field, type 1. Click OK.
7. Close the Registry Editor; then, restart your computer.
Precision and Scale for Apache Hive 0.13 Decimal Data Type
----------------------------------------------------------
When calling SQLGetInfo or SQLDescribeColumn against Hive 0.13
servers, the driver incorrectly returns a precision of 38 digits and
scale of 32 digits for the DECIMAL data type. Using the default
settings, the correct precision is 10 digits and the correct scale is
0 digits.
Oracle 12c Kerberos Authentication
----------------------------------
The driver has not been certified against Kerberos authentication on
Oracle 12c databases.
For Pivotal HAWQ Users
----------------------
The following are known limitations for using Pivotal
HAWQ with the Greenplum Wire Protocol driver:
*No support for updates.
*No support for deletes.
*No support for stored procedures.
Oracle XMLType Data Type
------------------------
The Oracle and Oracle Wire Protocol driver provide support for
XMLType columns, except those with binary or object relational
storage. Starting with Oracle 11.2.0.2, the default XML storage
type was changed from CLOB to BINARY. Consequently, columns created
simply as "XMLType" against Oracle 11.2.0.2 and later versions are not
supported by the drivers. An attempt to obtain the value of such a column
through the driver results in the exception "This column type is not
currently supported by this driver." To avoid this exception when
running the driver against Oracle 11.2.0.2 and later versions, change
the XML storage type to CHARACTER (CLOB) or use the TO_CLOB Oracle
function to cast the column.
SQL Server Wire Protocol Driver
-------------------------------
The SQL Server Wire Protocol driver requires an application to specify
the size of timestamp parameters when they are bound. Setting the option
WorkArounds2 to WorkArounds2=2 en
ables this behavior.
In addition, the driver does not allow an application to change the size
of parameter bindings between execute calls. Setting the option
WorkArounds to WorkArounds=536870912 enables this behavior.
Refer to the chapter "WorkAround Options" in the DATADIRECT CONNECT
SERIES FOR ODBC REFERENCE for a description of these options.
Upgrading from an Evaluation to a Licensed Installation
-------------------------------------------------------
If you have installed an evaluation copy of the drivers and want to
upgrade to a licensed version, you must use the Modify option of the
installation program.
Installing and Removing Default Data Sources
--------------------------------------------
When you first install a driver, you are given the option to install a
default data source for that driver. We recommend that you install
default data sources when you first install the drivers. If you do not
install the default data source at this time, you will be unable to
install a default data source for this driver later. To install a
default data source for a driver after the initial installation, you
must uninstall the driver and then reinstall it.
If you uninstall a 7.0 product after you have installed a 7.1 product,
default data sources that were created by the installer and share the
same name for both product versions will be removed from your machine.
For SSL Users
-------------
When trying to connect to a database using SSL encryption, you may
receive an error message similar to: "PRNG not seeded". This is because
certain versions of some operating systems do not generate truly random
numbers necessary for encryption. For more information about this error
and available patches, please refer to the Web site:
http://www.openssl.org/support/faq.html#USER1
SQLColAttribute(s)
------------------
The column attributes 1001 and 1002, which were assigned as DataDirect-
specific attributes, were inadvertently used as system attributes by
the Microsoft 3.0 ODBC implementation. Applications using those
attributes must now use 1901 and 1902, respectively.
SQL_C_NUMERIC
-------------
Because of inconsistencies in the ODBC specification, users attempting
to use SQL_C_NUMERIC parameters must set the precision and scale values
of the corresponding structure and the descriptor fields in the
Application Parameter Descriptor.
For Informix Users
------------------
Restriction: Some Informix error messages may contain more than one
error. All errors displayed may not be valid.
For Oracle 8 Server Users
-------------------------
The driver uses the XA protocol support in Oracle 8 to provide
distributed transaction support. For recovery to work correctly, you
must grant appropriate privileges on any server that will participate in
a distributed transaction. You must grant the SELECT privilege on
SYS.DBA_PENDING_TRANSACTIONS to all users that will use MTS. Refer to
the Oracle 8 documentation for details on using Oracle XA.
For Microsoft SQL Server Users
------------------------------
If you have problems with the catalog functions returning incorrect
data, you may need to upgrade your catalog stored procedures. Make
sure that you have installed the latest version of the stored
procedures, which are available from your database vendor. Refer to
your Microsoft SQL Server documentation for more information.
The SQL Server Wire Protocol drivers return stored procedure names with
the version number appended to them. For example, a procedure defined
as "proc1" will be returned as "proc1;1".
The SQL Server Legacy Wire Protocol driver does not support multiple
active statements on a single connection by default. See the Microsoft
document for information about how to enable multiple active statements
on a single connection using server-side cursors:
http://support.microsoft.com/kb/q140896/
When using the SQLDescribeParam method, the SQL Server Legacy Wire
Protocol driver describes parameters that map to the Microsoft SQL
Server 2008 date, time, datetime2, and datetimeoffset data types as
SQL_WVARCHAR.
The options listed in the "WorkAround Options" chapter of the DATADIRECT
CONNECT SERIES FOR ODBC REFERENCE cannot be used with the SQL Server
Legacy Wire Protocol driver.
For Btrieve Users
-----------------
The Btrieve driver may experience problems if the Btrieve Microkernel
Engine's communication buffer size is smaller than the Btrieve driver's
Array Size attribute. You can increase the communication buffer size
with the BTI Database Setup Utility. You can decrease the array size
option when you configure a data source using the ODBC Btrieve Setup
dialog, or when passing a connection string.
For Sybase Users
----------------
* For values of the real data type, to comply with the Sybase
server, the driver ensures the accuracy of the values
loaded through bulk load only up to 6 digits.
* For values of the money data type, to comply with the Sybase
server, if an application provides a scale (number of digits to
the right of the decimal) greater than 4, the driver truncates
it to 4.
* The driver does not support inserting data containing LOB columns
using the bulk load protocol. In such cases, the driver throws a
warning and falls back to the native protocol to continue executing
the inserts.
* When using Bulk load to execute an insert statement, the operation
will fail with an error message if non-identity columns are omitted
from the statement.
* You may experience a problem using catalog stored procedures when
running the Sybase Wire Protocol driver with Sybase Adaptive Server
11.5. Contact Sybase and ask for the latest version of their catalog
stored procedures.
On the Logon dialog box, there is a Database drop-down list that
displays the database names specified on the Connection tab of the ODBC
Sybase Wire Protocol Driver Setup dialog box. This functionality is
available in all cases except when connecting through the Test Connect
button on the Setup dialog box. When connecting through the Test
Connect button, only the default database specified on the General tab
of the Setup dialog box is available.
For Text Users
--------------
Restriction: When the Text driver encounters an invalid file, you may
receive duplicate or multiple errors.
For Flat-File Users
-------------------
If you are using a DataDirect Connect for ODBC flat-file driver, such
as dBASE under MSDASQL, use WorkArounds2=24 as described in the Driver
WorkAround Options chapter of the DATADIRECT CONNECT(R) SERIES FOR ODBC
REFERENCE.
Installing the XML Driver
-------------------------
You cannot have side-by-side installations of the DataDirect Connect
for ODBC XML 7.1 driver and the DataDirect Connect for ODBC XML 7.0
driver on your machine. After you install the 7.1 XML driver, the 7.0
XML driver will not work. If you uninstall the 6.1 XML driver after
installing the 7.1 driver, you must self-register the following two
XML files:
INIADX09.DLL
INXMLX09.DLL
For example, to self-register INIADX09.DLL, enter:
regsvr32 INIADX09.DLL
You must also have the Microsoft XML Parser installed. If you are
downloading the parser, as instructed in the DATADIRECT CONNECT SERIES
FOR ODBC USER'S GUIDE, be sure to download the complete package,
MSXML.MSI, not the sub-packages also available on the site.
For Developers Using IIS
------------------------
One of the most common connectivity issues encountered while using IIS
(Microsoft's Internet Information Server) concerns the use and settings
of the account permissions. If you encounter problems using DataDirect
drivers with an IIS server, refer to KnowledgeBase document number 4274
on the Progress DataDirect web site:
http://knowledgebase.datadirect.com.
For Microsoft Access Users
--------------------------
Some SQL implementations, such as PROGRESS, do not allow queries to
contain the COUNT function without the DISTINCT set quantifier. For
example, "SELECT COUNT(empid) FROM employees" is not a valid SQL query
for PROGRESS. This type of query can be generated using Microsoft
Access and results in an error.
For Users of the Driver for Apache Hive(TM)
-------------------------------------------
The following are notes, known problems, and restrictions with the
driver. These restrictions are based on using Apache Hive 0.10.0; other
versions of Apache Hive will have their own restrictions. You may
find a more complete listing of Apache Hive known issues and limitations
for your version of Apache Hive in the Apache Hive user
documentation here:
https://cwiki.apache.org/confluence/display/Hive/Home
Note that Apache Hive is not designed for OLTP workloads and does not
offer real-time queries or row-level updates. Apache Hive is instead
designed for batch type jobs over large data sets with high latency.
Known Issues for Apache Hive(TM)
-------------------------------
* No support for row-level inserts, updates, or deletes
* No difference between "NULL" and null values
* For HiveServer1 connections, no support for multiple simultaneous connections
per port
* For HiverServer1 connections, no support for user-level authentication
* For HiveServer1 connections, no support for canceling a running query
HiveQL
------
Apache Hive uses HiveQL, which provides much of the functionality of
SQL, but has some limitation syntax differences. For more information,
refer to the Hive Language Manual.
https://cwiki.apache.org/confluence/display/Hive/LanguageManual.
* A single quote within a string literal must be escaped
using a \ instead of using a single quote.
* Numeric values specified in scientific notation are not supported
in Hive 0.7.1.
* Apache Hive supports UNION ALL statements only when embedded in a
subquery. For example,
SELECT * FROM (SELECT integercol FROM itable UNION ALL
SELECT integercol FROM gtable2) result_table
* Join support is limited to equi-joins.
Driver Defects Resolved
-----------------------
PSC00093392 The driver took a long time to get the catalog of tables
for a typical application.
Notes for the Driver for Apache Hive(TM)
----------------------------------------
* Apache Hive does not support transactions, and by default, the
Driver for Apache Hive reports that transactions are not supported.
However, some applications will not operate with a driver that reports
transactions are not supported. The Transaction Mode connection option
allows you to configure the driver to report that it supports
transactions. In this mode, the driver ignores requests to enter manual
commit mode, start a transaction, or commit a transaction and return
success. Requests to rollback a transaction return an error regardless
of the transaction mode specified.
* The binary data type is not supported with HiveServer2.
For Users of the Impala Wire Protocol Driver
-------------------------------------------
The following are notes, known problems, and restrictions with the
driver. These restrictions are based on using Cloudera Impala server 1.0; other
versions of Impala will have their own restrictions. You may
find a more complete listing of Impala known issues and limitations
for your version of Cloudera Impala in the Cloudera Impala user
documentation here:
http://www.cloudera.com/content/support/en/documentation.html
Note that Impala is not designed for OLTP workloads and does not
offer real-time queries or row-level updates. Impala is instead
designed for batch type jobs over large data sets with high latency.
Known Issues for Cloudera Impala
-------------------------------
* No support for transactions
* No support for canceling a running query
* No support for row-level inserts, updates, or deletes
* No support for cursors or scrollable cursors
* No support for prepared statements
Notes for the Impala Wire Protocol driver
-----------------------------------------
* The Impala server uses the default port number 21050 unless changed by the
system administrator. Use this port number when configuring your driver or
consult with your system administrator.
* Do not use port number 21000 that is provided in the Beeswax and Cloudera
ODBC driver version 1.2 documentation unless your system administrator has
designated this as the port number for your connection. Using this port
number will return a connection error.
Documentation
PROGRESS DATADIRECT CONNECT SERIES FOR ODBC DOCUMENTATION SET
-------------------------------------------------------------
The Progress DataDirect Connect Series for ODBC documentation set is available
via product and data source tiles from the Progress Information Hub:
https://docs.progress.com
You can access the online help system directly via the HTML redirect in the
installation Help directory.
Installed Files for 32-bit Drivers
Database drivers are continually being added to each operating
environment. For the latest information about the specific drivers
available for your platform, refer to the Progress DataDirect database
support matrix Web page.
This file list assumes a full installation of all drivers. Your installation
may vary from this list depending on driver availability for your platform.
The installer copies the following file to the Windows system
directory:
IVTRC27.DLL DataDirect trace library
The installer copies the following files and subdirectories to the
product installation directory, by default, C:\Program
Files\Progress\DataDirect\Connect_for_ODBC_71:
NOTICES.TXT Third-party vendor license agreements
LICENSE.TXT Progress DataDirect license agreement
FIXES.TXT List of fixes since last release
ODBCREADME.TXT This file
\BIND:
\LUW\DDODBC_LUW.LST DB2 list files for Linux/UNIX/Windows
\LUW\DDOC510A.BND
\LUW\DDOC510B.BND
\LUW\DDOC510C.BND
\LUW\DDOR510A.BND
\LUW\DDOR510B.BND
\LUW\DDOR510C.BND
\LUW\DDOS510A.BND
\LUW\DDOS510B.BND
\LUW\DDOS510C.BND
\LUW\DDOU510A.BND
\LUW\DDOU510B.BND
\LUW\DDOU510C.BND
\iSeries\DDODBC_400.LST DB2 list files for DB2 for i
\iSeries\DDOC510A.BND
\iSeries\DDOC510B.BND
\iSeries\DDOC510C.BND
\iSeries\DDON510A.BND
\iSeries\DDON510B.BND
\iSeries\DDON510C.BND
\iSeries\DDOR510A.BND
\iSeries\DDOR510B.BND
\iSeries\DDOR510C.BND
\iSeries\DDOS510A.BND
\iSeries\DDOS510B.BND
\iSeries\DDOS510C.BND
\iSeries\DDOU510A.BND
\iSeries\DDOU510B.BND
\iSeries\DDOU510C.BND
\iSeries\DDOV5R2.SAVF
\iSeries\DDOV5R3.SAVF
\iSeries\DDOV5R4.SAVF
\iSeries\DDOV6R1.SAVF
\iSeries\DDOV7R1.SAVF
\iSeries\CfODBC iSeries Manual Package Creation Instructions.txt
\zOS\DDODBC_MVS.LST DB2 list files for z/OS
\zOS\CNTLFILE.XMIT
\zOS\DBRMFILE.XMIT
\zOS\DDOC510A.BND
\zOS\DDOC510B.BND
\zOS\DDOC510C.BND
\zOS\DDOR510A.BND
\zOS\DDOR510B.BND
\zOS\DDOR510C.BND
\zOS\DDOS510A.BND
\zOS\DDOS510B.BND
\zOS\DDOS510C.BND
\zOS\DDOU510A.BND
\zOS\DDOU510B.BND
\zOS\DDOU510C.BND
\zOS\CfODBC zOS Manual Package Creation Instructions.txt
\DRIVERS:
Resource library file names end in R; setup library file names end
in S.
INIADX09.DLL Support DLL for XML driver
INIADX09R.DLL
INXMLX09.DLL Support DLL for XML driver
INXMLX09R.DLL
IVASE27.DLL Sybase Wire Protocol driver
IVASE27R.DLL
IVBTR27.DLL Btrieve (Pervasive.SQL) driver
IVBTR27R.DLL
IVBTR27S.DLL
IVDB227.DLL DB2 Wire Protocol driver
IVDB227R.DLL
IVDBF27.DLL dBASE driver
IVDBF27R.DLL
IVGPLM27.DLL Greenplum Wire Protocol driver
IVGPLM27R.DLL (DataDirect Connect XE for ODBC)
IVHIVE27.DLL Driver for Apache Hive (DataDirect
IVHIVE27R.DLL Connect XE for ODBC)
IVICU27.DLL Unicode conversion tables
IVIMPALA27.DLL Impala Wire Protocol driver
(DataDirect Connect XE for ODBC)
IVIMPALA27R.DLL
IVIFCL27.DLL Informix Wire Protocol driver
IVIFCL27R.DLL
IVINF27.DLL Informix driver
IVINF27R.DLL
IVINF27S.DLL
IVINFDTC27.DLL
IVMSSS27.DLL SQL Server Legacy Wire Protocol driver
IVMSSS27R.DLL
IVMYSQL27.DLL MySQL Wire Protocol driver
IVMYSQL27R.DLL
IVODBC.LIC DataDirect driver license file
IVOE27.DLL Progress OpenEdge Wire Protocol driver
IVOE27R.DLL
IVOR827.DLL Oracle driver
IVOR827R.DLL
IVOR827S.DLL
IVOR8DTC27.DLL
IVORA27.DLL Oracle Wire Protocol driver
IVORA27R.DLL
IVPSQL27.DLL PostgreSQL Wire Protocol driver
IVPSQL27R.DLL
IVSFRC27.DLL Salesforce driver
(DataDirect Connect XE for ODBC)
IVSFRC27R.DLL
IVSFRC27S.DLL
IVSQLS27.DLL SQL Server Wire Protocol driver
IVSQLS27R.DLL
IVTLS27.DLL TLS/SSL support file
(OpenSSL Library File, version 1.1.1t)
IVSYIQ27.DLL Sybase IQ Wire Protocol driver
(DataDirect Connect XE for ODBC)
IVSYIQ27R.DLL
IVTERA27.DLL Teradata driver
(DataDirect Connect XE for ODBC)
IVTERA27R.DLL
IVTERA27S.DLL
IVTRC27.DLL DataDirect trace library
IVTRN27.DLL DataDirect sample translation DLL
IVTXT27.DLL Text driver
IVTXT27R.DLL
IVXML27.DLL XML driver
IVXML27R.DLL
IVXML27S.DLL
QESQLEXT.H Header file for DataDirect-specific ODBC
Definitions
\HELP:
ConnectforODBCHelp.html HTML redirect to online help system
\JAVA\LIB:
*.* Files associated with the Salesforce driver
SFORCE.JAR Java components for the Salesforce driver
\JRE
*.* Files associated with the Salesforce driver
\SAMPLES:
\BULK\BULK.C Bulk example source
\BULK\BULK.EXE Bulk application
\BULK\BULK.MAK Bulk example make file
\BULK\BULK.SLN Bulk example solution file
\BULK\BULK.VCPROJ Bulk example project file
\BULK\BULK.TXT Bulk example description
\BULK\DDLOGGING.PROPERTIES Log configuration file for the Salesforce
driver
\BULKSTRM\BULK.CPP Bulk streaming example source
\BULKSTRM\BULK.HPP Bulk streaming example header
\BULKSTRM\BULK.RC Bulk streaming example resource file
\BULKSTRM\BULKSTRM.TXT Bulk streaming description
\BULKSTRM\BULKSTREAMING.SLN Bulk streaming example solution file
\BULKSTRM\BULKSTREAMING.VCPROJ Bulk streaming example project file
\BULKSTRM\BULKSTRM.EXE Bulk streaming example application
\BULKSTRM\DDLOGGING.PROPERTIES Log configuration file for the
Salesforce driver
\BULKSTRM\MSGPRINTF.HPP Bulk streaming example header file
\BULKSTRM\PROGRESSDATADIRECT.BMP
\BULKSTRM\PROGRESSDATADIRECT.ICO
\BULKSTRM\WINMAIN.CPP Bulk streaming example source file
\EXAMPLE\DDLOGGING.PROPERTIES Log configuration file for the Salesforce
driver
\EXAMPLE\EXAMPLE.C Example source
\EXAMPLE\EXAMPLE.EXE Example application
\EXAMPLE\EXAMPLE.H Example header
\EXAMPLE\EXAMPLE.MAK Example make file
\EXAMPLE\EXAMPLE.SLN Example solution file
\EXAMPLE\EXAMPLE.VCPROJ Example project file
\EXAMPLE\EXAMPLE.TXT Example description
\TRANSLAT\LIBMAIN.C
\TRANSLAT\README.TRN Translation Library example description
\TRANSLAT\TRANSLAT.C Translation Library example source file
\TRANSLAT\WINNT.MAK Translation Library example make file
\TOOLS:
DDEXTWIN.EXE License Extender utility
DDPROCINFO.EXE Processor Information utility
DSNCONVERTERSIL.EXE Data Source Converter utility
XMLP.EXE A GUI demo tool that persists a result set to
an XML data file
salesforceserver.exe
ddextwin.exe
\TOOLS\POWER BI:
DATADIRECTGREENPLUM.PQX Greenplum Power BI connector file
DATADIRECTPOSTGRESQL.PQX PostgreSQL Power BI connector file
INSTALL.BAT Batch file to install Power BI connectors
\UNINSTALL PROGRESS DATADIRECT CONNECT AND CONNECT XE FOR ODBC
\*.* Files used to uninstall the product
Progress_DataDirect_Connect_and_Connect_XE_for_ODBC_7.1_InstallLog.log
Installation log file
\%USERPROFILE%:
CfODBC7.1_install_console.log Installation log file
\WIZARDS:
INDEX.HTML
ODBCPERF.JAR Performance wizard
\IMAGES\*.*
Installed Files for 64-bit Drivers
Database drivers are continually being added to each operating
environment. For the latest information about the specific drivers
available for your platform, refer to the Progress DataDirect database
support matrix Web page.
This file list assumes a full installation of all drivers. Your installation
may vary from this list depending on driver availability for your platform.
The installer copies the following file to the Windows system
directory:
DDTRC27.DLL DataDirect trace library
The installer copies the following files and subdirectories to the
product installation directory, by default, C:\Program
Files\Progress\DataDirect\Connect64_for_ODBC_71:
NOTICES.TXT Third-party vendor license agreements
LICENSE.TXT Progress DataDirect license agreement
ODBC64FIXES.TXT List of fixes since last release
ODBC64README.TXT This file
\BIND:
\LUW\DDODBC_LUW.LST DB2 list files for Linux/UNIX/Windows
\LUW\DDOC510A.BND
\LUW\DDOC510B.BND
\LUW\DDOC510C.BND
\LUW\DDOR510A.BND
\LUW\DDOR510B.BND
\LUW\DDOR510C.BND
\LUW\DDOS510A.BND
\LUW\DDOS510B.BND
\LUW\DDOS510C.BND
\LUW\DDOU510A.BND
\LUW\DDOU510B.BND
\LUW\DDOU510C.BND
\iSeries\DDODBC_400.LST DB2 list files for DB2 for i
\iSeries\DDOC510A.BND
\iSeries\DDOC510B.BND
\iSeries\DDOC510C.BND
\iSeries\DDON510A.BND
\iSeries\DDON510B.BND
\iSeries\DDON510C.BND
\iSeries\DDOR510A.BND
\iSeries\DDOR510B.BND
\iSeries\DDOR510C.BND
\iSeries\DDOS510A.BND
\iSeries\DDOS510B.BND
\iSeries\DDOS510C.BND
\iSeries\DDOU510A.BND
\iSeries\DDOU510B.BND
\iSeries\DDOU510C.BND
\iSeries\DDOV5R2.SAVF
\iSeries\DDOV5R3.SAVF
\iSeries\DDOV5R4.SAVF
\iSeries\DDOV6R1.SAVF
\iSeries\DDOV7R1.SAVF
\iSeries\CfODBC iSeries Manual Package Creation Instructions.txt
\zOS\DDODBC_MVS.LST DB2 list files for z/OS
\zOS\CNTLFILE.XMIT
\zOS\DBRMFILE.XMIT
\zOS\DDOC510A.BND
\zOS\DDOC510B.BND
\zOS\DDOC510C.BND
\zOS\DDOR510A.BND
\zOS\DDOR510B.BND
\zOS\DDOR510C.BND
\zOS\DDOS510A.BND
\zOS\DDOS510B.BND
\zOS\DDOS510C.BND
\zOS\DDOU510A.BND
\zOS\DDOU510B.BND
\zOS\DDOU510C.BND
\zOS\CfODBC zOS Manual Package Creation Instructions.txt
\DRIVERS:
Resource library file names end in R; setup library file names end
in S.
DDEXTWIN.EXE License Extender utility
DDASE27.DLL Sybase Wire Protocol driver
DDASE27R.DLL
DDDB227.DLL DB2 Wire Protocol driver
DDDB227R.DLL
DDGPLM27.DLL Greenplum driver driver
DDGPLM27R.DLL
DDHIVE27.DLL Driver for Apache Hive [DataDirect
DDHIVE27R.DLL Connect64 XE for ODBC only]
DDICU27.DLL Unicode conversion tables
DDIMPALA27.DLL Impala Wire Protocol Driver
DDIMPALA27R.DLL
DDIFCL27.DLL Informix Wire Protocol driver
DDIFCL27R.DLL
DDMSSS27.DLL SQL Server Legacy Wire Protocol driver
DDMSSS27R.DLL
DDMYSQL27.DLL MySQL Wire Protocol driver
DDMYSQL27R.DLL
DDODBC.LIC DataDirect license file
DDOR827.DLL Oracle driver
DDOR827R.DLL
DDOR827S.DLL
DDOR8DTC27.DLL
DDORA27.DLL Oracle Wire Protocol driver
DDORA27R.DLL
DDPSQL27.DLL PostgreSQL driver driver
DDPSQL27R.DLL
DDOE27.DLL Progress OpenEdge Wire Protocol driver
DDOE27R.DLL
DDSFRC27.DLL Salesforce driver
DDSFRC27R.DLL
DDSFRC27S.DLL
DDSQLS27.DLL SQL Server Wire Protocol driver
DDSQLS27R.DLL
DDTLS27.DLL TLS/SSL support file
(OpenSSL Library File, version 1.1.1t)
DDSYIQ27.DLL Sybase IQ Wire Protocol driver
DDSYIQ27R.DLL
DDTERA27.DLL Driver for the Teradata database [only on
Itanium II]
DDTERA27R.DLL
DDTERA27S.DLL
DDTRC27.DLL DataDirect trace library
DDTRN27.DLL DataDirect sample translation DLL
DDTXT27.DLL Text driver
DDTXT27R.DLL
LICENSE.INI License information file
QESQLEXT.H Header file for DataDirect-specific ODBC
Definitions
\HELP:
ConnectforODBCHelp.html HTML redirect to online help system
\JAVA\LIB:
*.* Files associated with the Salesforce driver
SFORCE.JAR Java components for the Salesforce driver
\SAMPLES:
\BULK\BULK.C Bulk example source
\BULK\BULK.EXE Bulk application
\BULK\BULK.SLN Bulk example solution file
\BULK\BULK.VCPROJ Bulk example project file
\BULK\BULK.TXT Bulk example description
\BULK\DDLOGGING.PROPERTIES Log configuration file for the Salesforce
driver
\BULK\BULK.MAK Bulk example make file (used instead of .SLN
and .VCPROJ files on Itanium 64 only)
\BULKSTRM\BULK.CPP Bulk streaming example source
\BULKSTRM\BULK.HPP Bulk streaming example header
\BULKSTRM\BULK.RC Bulk streaming example resource file
\BULKSTRM\BULKSTRM.TXT Bulk streaming description
\BULKSTRM\BULKSTREAMING.SLN Bulk streaming example solution file
\BULKSTRM\BULKSTREAMING.VCPROJ Bulk streaming example project file
\BULKSTRM\BULKSTRM.EXE Bulk streaming example application
\BULKSTRM\DDLOGGING.PROPERTIES Log configuration file for the
Salesforce driver
\BULKSTRM\MSGPRINTF.HPP Bulk streaming example header file
\BULKSTRM\PROGRESSDATADIRECT.BMP
\BULKSTRM\PROGRESSDATADIRECT.ICO
\BULKSTRM\WINMAIN.CPP Bulk streaming example source file
\BULKSTRM\BULK.MAK Bulk streaming example make file
\EXAMPLE\DDLOGGING.PROPERTIES Log configuration file for the Salesforce
driver
\EXAMPLE\EXAMPLE.C Example source
\EXAMPLE\EXAMPLE.EXE Example application
\EXAMPLE\EXAMPLE.H Example header
\EXAMPLE\EXAMPLE.SLN Example solution file
\EXAMPLE\EXAMPLE.VCPROJ Example project file
\EXAMPLE\EXAMPLE.TXT Example description
\EXAMPLE\EXAMPLE.MAK Example make file (used instead of .SLN and
.VCPROJ files on Itanium 64 only)
\TRANSLAT\LIBMAIN.C
\TRANSLAT\README.TRN Translation Library example description
\TRANSLAT\TRANSLAT.C Translation Library example source file
\TRANSLAT\WINNT.MAK Translation Library example make file
\TOOLS:
DDEXTWIN.EXE License Extender utility
DDPROCINFO.EXE Processor Information utility
DSNCONVERTERSIL.EXE Data Source Converter utility
XMLP.EXE A GUI demo tool that persists a result set to
an XML data file
salesforceserver.exe
ddextwin.exe
\TOOLS\POWER BI:
DATADIRECTGREENPLUM.PQX Greenplum Power BI connector file
DATADIRECTPOSTGRESQL.PQX PostgreSQL Power BI connector file
INSTALL.BAT Batch file to install Power BI connectors
\UNINSTALL PROGRESS DATADIRECT CONNECT64(R) AND CONNECT64 XE FOR ODBC 7.1
\*.* Files used to uninstall the product
Progress_DataDirect_Connect64_and_Connect64_XE_for_ODBC_7.1_InstallLog.log
Installation log file
\WIZARDS:
INDEX.HTML
ODBCPERF.JAR Performance wizard
\IMAGES\*.*
~~~~~~~~~~~~~~
February 2026
End of README