SQL Server ODBC 8.0.2 Windows
- Last Updated: May 8, 2026
- 17 minute read
- OpenAccess SDK
- Documentation
README
Progress(R) DataDirect(R)
Progress DataDirect for ODBC for SQL Server Wire Protocol Driver
Windows Platforms (32- and 64-bit)
8.0.2 Release
April 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(R)
for ODBC SQL Server(TM) Wire Protocol Driver.
This README file contains information not included in the PROGRESS
DATADIRECT FOR ODBC FOR SQL SERVER USER'S GUIDE AND REFERENCE.
CONTENTS
Post-GA Product Announcements
Requirements
Installation Directory
Data Source and Platform Support
Third-party Components Compatibility Matrix
Changes Since 8.0.2 GA
Changes for 8.0.2 GA
Driver WorkAround Options
Notes, Known Problems, and Restrictions
Documentation
Installed Files for the 32-bit Driver
Installed Files for the 64-bit Driver
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).
Requirements
* The installer program requires a JVM that is Java SE 11 or higher, including
Oracle JDK, OpenJDK, and IBM SDK (Java) distributions.
* The driver requires the following runtime library:
Microsoft Visual C/C++ runtime version 14.40.33810 or higher
* 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.
Installation Directory
* The default installation directory for the 32-bit driver on a 64-bit
system is:
C:\Program Files (86)\Progress\DataDirect\ODBC
* The default installation directory for all other installations is:
C:\Program Files\Progress\DataDirect\ODBC
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
Third-party Components Compatibility Matrix
For information about the third-party components that are installed with the
product, refer to the ODBC Third-party Components Compatibility Matrix on the
DataDirect Product Life Cycle page:
https://docs.progress.com/bundle/datadirect-product-life-cycle/page/topics/
datadirect_life_cycle/datadirect-product-life-cycle.html
Changes Since 8.0.2 GA
Debugging Symbols
-----------------
The product package now includes .pdb files. These files contain debugging
symbols that can be used for diagnosing and debugging issues in the driver.
Support for Microsoft Fabric
----------------------------
The driver now provides read-write access to the Synapse Data Warehouse
endpoints of Microsoft Fabric. For more information, including limitations,
refer to the user's guide.
Available: 08.02.2150 (B3227, U3190)|04/14/2025
Windows Runtime Version Upgrade
-------------------------------
The driver is now compiled with a Visual Studio 2022 compiler for Windows
platforms. As a result, you must have Microsoft Visual C/C++ runtime
version 14.40.33810 or higher on your machine to run the driver.
PKCS# 12 Files
--------------
The driver has been enhanced to support PKCS #12 files as keystore providers
for the Always Encrypted feature. PKCS #12 files can be stored locally on
the disk on any platform the driver supports. You can configure the driver
to use a PKCS #12 file using the new AE Keystore Location (AEKeyStoreLocation)
and AE Keystore Secret (AEKeyStoreSecret) connection options. Refer to the
user's guide for details.
JRE Requirement for the Installer
---------------------------------
The installer program now requires you to install a JRE that is Java SE 11 or
higher before running the installer. In earlier versions, the JRE used by the
installer program was included in the product. However, to avoid potential
security vulnerabilities, the installer program no longer includes a JRE.
Instead, the installer program uses the JRE in your environment to allow for
the most secure version of a JRE to be used.
Notes:
* This change does not affect the JVM requirements for the driver. For the latest
driver requirements, refer to the Product Compatibility Guide:
https://docs.progress.com/bundle/datadirect-product-compatibility/resource/
datadirect-product-compatibility.pdf
* The installer program cannot remove the already installed JRE files from the
install directory automatically. Remove them manually.
Entra ID Authentication Using Managed Identities
------------------------------------------------
The driver has been enhanced to support Microsoft Entra ID authentication using
managed identities for Azure resources. You can configure this feature using
the updated Authentication Method (AuthenticationMethod) and User Name
(LogonID) options.
Entra ID Authentication Using Service Principal Users
----------------------------------------------------
The driver has been enhanced to support Microsoft Entra ID authentication using
service principal users. You can configure this feature using the updated
Authentication Method (AuthenticationMethod), User Name (LogonID) and Password
(Password) options.
ICU Library Upgrade (74.1)
--------------------------
The ICU library files that are installed with the product have been
upgraded to version 74.1. As a part of this upgrade, the ICU library
file names have changed:
* For the 32-bit driver: From ivicu28.dll to ivicu.dll
* For the 64-bit driver: From ddicu28.dll to ddicu.dll
This upgrade is available starting in build 08.02.1072 of the ICU
library files.
TLSv1.3 Support
---------------
The driver has been enhanced to support the TLSv1.3 cryptographic protocol
using SQL Server 2022. To enable TLSv1.3 encryption, set the Encryption Method
(EncryptionMethod) option to the new value 8 (Strict).
SSL Enhancement (3.0.9)
-----------------------
Note: OpenSSL library 3.0.9 has been replaced with a later version. For
the latest information about the third-party components that are installed
with the product, refer to the ODBC Third-party Components Compatibility
Matrix on the DataDirect Product Life Cycle page:
https://docs.progress.com/bundle/datadirect-product-life-cycle/page/topics/
datadirect_life_cycle/datadirect-product-life-cycle.html.
The default version of the OpenSSL library has been upgraded to version
3.0.9, which fixes the security vulnerabilities listed on the following
page: https://www.openssl.org/news/vulnerabilities-3.0.html
This upgrade is available in build 08.02.0595 of the following OpenSSL
library files: ivopenssl30.dll (32-bit) and ddopenssl30.dll (64-bit).
Notes:
* The driver supports the following OpenSSL 3.0 providers: Default and
FIPS.
* The FIPS provider is supported only on the following platforms:
Windows 64-bit, Linux 64-bit, and AIX 64-bit.
* The following connection options have been added to configure the
driver to use OpenSSL 3.0: Enable FIPS (EnableFIPS), OpenSSL Config File
(OpenSSLConfigFile), and OpenSSL Provider Path (OpenSSLProviderPath).
For more information on the new connection options and how to configure
the driver to use OpenSSL 3.0, refer to the user's guide.
* When installing a new version of the product, the installer program will
automatically replace the OpenSSL 1.1.1 library files with the OpenSSL 3.0
library files in the install directory, which will impact all the DataDirect
ODBC drivers installed on a machine. Therefore:
- If you are using multiple 8.0 drivers, upgrade all your drivers to the latest
version.
- If you are using both 8.0 and 7.1 versions of the driver, copy the xxtls27.dll
file to a different location before installing a new version of the 8.0 driver.
Copy it back to the install directory once the installation is complete.
End of Support for OpenSSL 1.1.1
--------------------------------
The product no longer includes version 1.1.1 of the OpenSSL library.
The library will reach the end of its product life cycle in September 2023
and will not receive any security updates after that. Note that continuing
to use the library after September 2023 can potentially expose you to
security vulnerabilities.
Note: As a result of this change, when installing a new version of the product,
the installer program will automatically remove version 1.1.1 of the library
from the install directory, which will impact all the DataDirect ODBC drivers
installed on a machine.
Installer Upgrade
-----------------
The installer program has been enhanced to use a more modern and
secure technology. As a result of this enhancement:
* The default installation location has been changed to:
- For the 32-bit driver on a 64-bit system:
C:\Program Files (86)\Progress\DataDirect\ODBC
- For all other installations:
C:\Program Files\Progress\DataDirect\ODBC
* The new installer program does not support upgrading installations
made with earlier versions of the installer. You will need to
uninstall the existing installation and reinstall with the new
installer to resume upgrades in the same directory.
* The existing data sources cannot be used until they are
updated to point to the new installation location. To learn
how to update them, refer to the best practices documented
at https://community.progress.com/s/.
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.
Fetching Collation Sequence from the Server When Executing
SQLGetInfo(SQL_COLLATION_SEQ)
-----------------------------------------------------------------
When executing SQLGetInfo(SQL_COLLATION_SEQ) against:
* SQL Server version 2005 and later, the driver now fetches the collation
sequence from the server. It earlier returned ISO 8859-1 as the collation
sequence for every fetch.
* SQL Server versions prior to 2005, the driver continues to return ISO 8859-1
as the collation sequence.
Support for Windows Certificate Store
-------------------------------------
The driver has been enhanced to support the Windows certificate store for
TLS/SSL server authentication. Refer to the user's guide for details.
Support for TLS/SSL Server Authentication in a Serverless Environment
---------------------------------------------------------------------
The driver has been enhanced to support TLS/SSL server authentication for
the applications deployed in a serverless environment. The driver stores the
TLS/SSL certificates in memory and lets applications use TLS/SSL server
authentication without storing the truststore file on the disk. To use this
enhancement, specify the content of the certificate in the refreshed
Trust Store (Truststore) connection option or the new
SQL_COPT_INMEMORY_TRUSTSTORECERT pre-connection attribute. Refer to the
user's guide for details.
Server Alias Support
--------------------
The driver has been enhanced to support connecting to servers using aliases
created by the SQL Server Configuration Manager. To support this feature, the
Host Name (HostName) connection option has been refreshed to accept alias names
as valid values. The driver uses the server name and port number provided by
the alias when establishing a connection.
Returning SQL_SERVER_NAME With SQLGetInfo
-----------------------------------------
The driver has been updated to return the server name to which you are
connected for the value of SQL_SERVER_NAME when executing SQLGetInfo. In
earlier versions of the driver, the value returned for SQL_SERVER_NAME
would be the setting of the Host Name (HostName) connection option. The
driver will now return the server name string that it receives from the server
when connecting to the database as the value for SQLGetInfo(SQL_SERVER_NAME).
Keep Active Connections Enhancement
-----------------------------------
The driver has been enhanced with the new Keep Connection Active
(KeepConnectionActive) and Socket Idle Time (SocketIdleTimeCheckInterval)
connection options. Together, these options provide you with a method to keep
active idle connections to Azure SQL Database, Azure Synapse Analytics through
Azure SQL Gateway, or to databases that enforce timeouts for inactivity.
Enable Replication User feature for IDENTITY columns
----------------------------------------------------
The driver has been enhanced to support inserts into SQL Server IDENTITY
columns in replication scenarios. Either the Enable Replication User
(EnableReplicationUser) connection option or the SQL_COPT_REPLICATION_USER
connection attribute (numeric value 1080) can be used to allow inserts into
IDENTITY columns. When the replication user feature is set to 1 (Enabled),
explicit values can be inserted into IDENTITY columns defined as
NOT FOR REPLICATION. If different values are specified for the
Enable Replication User option and the SQL_COPT_REPLICATION_USER attribute,
driver behavior is determined by the value of the SQL_COPT_REPLICATION_USER
attribute.
XA Interface Support
--------------------
The driver has been enhanced to support distributed transactions.
It implements the XA interface to enable support for distributed transactions.
For details, refer to the user's guide.
Documentation
-------------
Any product package made available after February 9, 2021 will not include the
HTML help system or user's guide PDF. The full documentation set, including
these items, is available from the Progress Information Hub:
https://docs.progress.com/category/datadirect-microsoft-sql-server
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.
Note that all Progress DataDirect for ODBC documentation has been migrated to
the Progress Information Hub:
https://docs.progress.com/
Access Token Authentication Support
-----------------------------------
The driver has been enhanced to support access token authentication
programmatically with the use of a pre-connection attribute
SQL_COPT_SS_ACCESS_TOKEN. Refer to the user's guide for more information.
sp_describe_undeclared_parameters Support
-----------------------------------------
The driver has been enhanced to use sp_describe_undeclared_parameters, a SQL
Server system stored procedure, to fetch parameter metadata. With this
enhancement, the driver can return more accurate parameter metadata for both
simple and complex queries. However, it cannot determine if a parameter allows
NULL values; hence, it returns SQL_NULLABLE_UNKNOWN for the nullable fields.
Note that the driver does not call sp_describe_undeclared_parameters to fetch
parameter metadata when Always Encrypted functionality is enabled
(ColumnEncryption=Enabled).
Timestamp Logging in Packet Logs
--------------------------------
The drivers using base version B0649 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.
Always Encrypted Support
------------------------
The driver has been enhanced to support the Always Encrypted feature. Beginning
with SQL Server 2016, Azure SQL and SQL Server databases support Always
Encrypted, which allows sensitive data to be stored on the server in an
encrypted state such that the data can only be decrypted by an authorized
application. The following are highlights of this enhancement:
* The driver detects all supported native data types in encrypted columns and
transparently encrypts values bound to SQL parameters or decrypts values
returned in results and output parameters.
* The driver supports configurable caching of column encryption keys for
improved performance.
* The driver supports using Windows Certificate Store and Azure Key Vault as
keystore providers.
You can enable support for Always Encrypted using the new Column Encryption,
Key Store Principal, Key Store Secret, and Key Cache Time To Live connection
options. Refer to the user's guide for more information.
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 \drivers subdirectory. Refer to
the user's guide for more information.
Changes for the 8.0.2 GA
Support for Microsoft Azure Synapse Analytics and
Microsoft Analytics Platform System
--------------------------------------------------
The driver has been enhanced to transparently connect to Microsoft Azure
Synapse Analytics and Microsoft Analytics Platform System data sources.
For more information about supported features and functionality, refer
to "Support for Microsoft Azure Synapse Analytics and Analytics Platform
System" in the user's guide.
HTTP Proxy Support
------------------
Support for connecting to a proxy server through an HTTP connection. HTTP
proxy support is configurable with five new connection options: Proxy Host,
Proxy Mode, Proxy Password, Proxy Port, and Proxy User.
Enable Server Side Cursors Connection Option
--------------------------------------------
The new EnableServerSideCursors connection option allows you to determine
which server-side cursors are enabled for the data source.
Azure AD 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.
Always On Availability Groups
-----------------------------
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 new Multi-Subnet Failover option allows the driver to attempt parallel
connections to all the IP addresses associated with an availability group
listener when the primary listener is unavailable. This offers improved
response time over traditional failover, which attempts connections to
alternate servers one at a time. This option must be enabled for failover to
work properly in an Always On environment.
- 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.
Default Value for Crypto Protocol Version
-----------------------------------------
The default value for Crypto Protocol Version has been updated to TLSv1.2,
TLSv1.1,TLSv1. This change improves the security of the driver by employing
only the most secure cryptographic protocols as the default behavior.
Driver WorkAround Options
Progress DataDirect has included non-standard connection options (workarounds)
for the driver 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 PROGRESS DATADIRECT FOR ODBC DRIVERS REFERENCE for a
description of these options.
Notes, Known Issues, and Restrictions
Character Limit of the Trust Store Field (Driver setup dialog)
---------------------------------------------------------------
The Trust Store field on the Driver setup dialog supports content up to 8192
characters in length. For specifying certificate content longer than 8192
characters, edit the registry and manually add the entry to the DSN.
Specifying values for the same connection option multiple times
---------------------------------------------------------------
The driver does not support specifying values for the same connection
option multiple times in a connection string or DSN. If a value is
specified using the same attribute multiple times or using both
long and short attributes, the connection may fail or the driver may
not behave as intended.
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.
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 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.
Binding Timestamp Parameters
----------------------------
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 enables 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 user's guide and reference
for a description of these options.
Microsoft SQL Server Limitations
--------------------------------
Attempting to execute DDL statements that contain errors causes
an implicit rollback of the current transaction if executing in
manual commit mode. No warning occurs when this happens. This is a
Microsoft SQL Server limitation, and no driver workaround is available.
NOTE: Because the SQL Server Wire Protocol drivers do not have a way to
prepare statements, the driver does not send those statements to the
server until SQLExecute is called. PREPARE does not return any of the
normal errors that most of the drivers return. If, however, the user
requests information about result columns, the driver executes a Select
statement and returns warnings or errors when using SQLNumResultCols,
SQLDescribeCol, or SQLColAttributes.
Catalog Functions
-----------------
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".
For Microsoft Access Users
--------------------------
Some SQL implementations, do not allow queries to contain the COUNT function
without the DISTINCT set quantifier. For example,
"SELECT COUNT(empid) FROM employees" would be considered an invalid SQL query
by the database engine. This type of query can be generated using Microsoft
Access and results in an error.
Documentation
PROGRESS DATADIRECT FOR ODBC FOR SQL SERVER WIRE PROTOCOL DOCUMENTATION SET
---------------------------------------------------------------------------
The driver documentation set is available from the Progress Information Hub:
https://docs.progress.com/category/datadirect-microsoft-sql-server
You can access the online help system directly via the HTML redirect in the
installation Help directory.
Uninstalling the Driver
You can uninstall the product or individual drivers through the Uninstall
DataDirect for ODBC 8.0 option in the DataDirect program group.
Installed Files the 32-bit Driver
This file list assumes a full installation of the driver and
documentation.
The installer copies the following file to the Windows system
directory:
ivtrc28.dll DataDirect trace library
The installer copies the following files and subdirectories to the
product installation directory, by default:
For the 32-bit driver on 64-bit machines:
C:\Program Files (86)\Progress\DataDirect\ODBC
For all other installations:
C:\Program Files\Progress\DataDirect\ODBC
fixes.txt List of fixes since last release
license.txt Progress DataDirect license agreement
\drivers:
ivcurl28.dll Library used for HTTP connection
ivcurl28.pdb Debugging symbols for Curl library
ivicu.dll Unicode conversion tables
ivicu.pdb Debugging symbols for ICU library
ivsqls28.dll SQL Server Wire Protocol Driver
ivsqls28.pdb Debugging symbols for SQL Server
Wire Protocol Driver
ivsqls28r.dll SQL Server Wire Protocol Driver
resource file
IVODBC.LIC DataDirect license file
ivopenssl30.dll TLS/SSL support file (OpenSSL library file,
version 3.0)
ivopenssl30.pdb Debugging symbols for OpenSSL 3.0 library
ivopenssl.dll TLS/SSL support file (OpenSSL library file,
version 3.5)
ivopenssl.pdb Debugging symbols for OpenSSL 3.5 library
ivtrc28.dll DataDirect trace library
ivtrc28.pdb Debugging symbols for DataDirect trace library
qesqlext.h Header file for DataDirect-specific ODBC
Definitions
\help:
*.html HTML redirects to online connector help
systems and documentation resources
\NOTICES:
ODBC for SQL Server
8.0 NOTICES.TXT Third-party vendor license agreements
\READMES:
ODBC FOR SQL Server
8.0 README.TXT This file
\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
\bulkstrm\bulk.cpp Bulk streaming example source
\bulkstrm\bulk.hpp Bulk streaming example header
\bulkstrm\bulk.rc Bulk streaming example resource file
\bulkstrm\bulkstreaming.sln Bulk streaming example solution file
\bulkstrm\bulkstreaming.vcproj Bulk streaming example project file
\bulkstrm\bulkstrm.exe Bulk streaming example application
\bulkstrm\bulkstrm.txt Bulk streaming description
\bulkstrm\msgprintf.hpp Bulk streaming example header file
\bulkstrm\ProgressDataDirect.bmp
\bulkstrm\ProgressDataDirect.ico
\bulkstrm\winmain.cpp Bulk streaming example source file
\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
\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
\UNINSTALL\*.* Files used to uninstall the product
Installed Files for the 64-bit Driver
This file list assumes a full installation of all drivers and
documentation.
The installer copies the following file to the Windows system
directory:
ddtrc28.dll DataDirect trace library
The installer copies the following files and subdirectories to the
product installation directory, by default:
C:\Program Files\Progress\DataDirect\ODBC\:
fixes.txt List of fixes since last release
license.txt Progress DataDirect license agreement
\drivers:
ddcurl28.dll Library used for HTTP connection
ddcurl28.pdb Debugging symbols for Curl library
ddicu.dll Unicode conversion tables
ddicu.pdb Debugging symbols for ICU library
ddsqls28.dll SQL Server Wire Protocol Driver
ddsqls28.pdb Debugging symbols for SQL Server
Wire Protocol Driver
ddsqls28r.dll SQL Server Wire Protocol Driver
resource file
DDODBC.LIC DataDirect license file
ddopenssl30.dll TLS/SSL support file (OpenSSL library file,
version 3.0)
ddopenssl30.pdb Debugging symbols for OpenSSL 3.0 library
ddopenssl.dll TLS/SSL support file (OpenSSL library file,
version 3.5)
ddopenssl.pdb Debugging symbols for OpenSSL 3.5 library
ddtrc28.dll DataDirect trace library
ddtrc28.pdb Debugging symbols for DataDirect trace library
fips.dll Support file for FIPS provider
fips.pdb Debugging symbols for FIPS provider
openssl.cnf Configuration file for FIPS provider
qesqlext.h Header file for DataDirect-specific ODBC
Definitions
\help:
*.html HTML redirects to online connector help
systems and documentation resources
\NOTICES:
ODBC for SQL Server
8.0 NOTICES.TXT Third-party vendor license agreements
\READMES:
ODBC for SQL Server
8.0 README.TXT This file
\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
\bulkstrm\bulk.cpp Bulk streaming example source
\bulkstrm\bulk.hpp Bulk streaming example header
\bulkstrm\bulk.rc Bulk streaming example resource file
\bulkstrm\bulkstreaming.sln Bulk streaming example solution file
\bulkstrm\bulkstreaming.vcproj Bulk streaming example project file
\bulkstrm\bulkstrm.exe Bulk streaming example application
\bulkstrm\bulkstrm.txt Bulk streaming description
\bulkstrm\msgprintf.hpp Bulk streaming example header file
\bulkstrm\ProgressDataDirect.bmp
\bulkstrm\ProgressDataDirect.ico
\bulkstrm\winmain.cpp Bulk streaming example source file
\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
\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
\UNINSTALL\*.* Files used to uninstall the product
~~~~~~~~~~~~~~~~
April 2026
End of README