MongoDB ODBC 8.1.0 Windows
- Last Updated: May 8, 2026
- 17 minute read
- OpenAccess SDK
- Documentation
README
Progress(R) DataDirect(R)
Progress(R) DataDirect(R) for ODBC for MongoDB(TM)
Windows Platforms (32- and 64-bit)
Release 8.1.0
February 2026
***********************************************************************
Copyright (C) 2026 Progress Software Corporation and/or its
subsidiaries or affiliates. All Rights Reserved.
***********************************************************************
CONTENTS
Post-GA Product Announcements
Installation Directory
Requirements
Data Source and Platform Support
Changes Since 8.1.0 GA
Changes for 8.1.0 GA
DataDirect ODBC Driver Configuration Manager
Notes, Known Problems, and Restrictions
Driver Workaround Options
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 the 32-bit driver on a 64-bit
system is:
C:\Program Files (x86)\Progress\DataDirect\ODBC
* The default installation directory for all other installations is:
C:\Program Files\Progress\DataDirect\ODBC
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 a Java Virtual Machine (JVM): Java SE, version 8 or
higher, including Oracle JDK, OpenJDK, IBM SDK (Java), or higher
LTS versions.
* 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.
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 8.1.0 GA
CVE-2022-41853 - Use of Externally-Controlled Input to Select Classes or Code
('Unsafe Reflection')
-----------------------------------------------------------------------------
Several Progress DataDirect ODBC drivers utilized a version of HyperSQL
Database that was vulnerable to remote code execution described in
CVE-2022-41853. All impacted drivers have been patched to fix this
vulnerability. For details on impacted drivers and fixed versions, refer to
the following KB article:
https://community.progress.com/s/article/DataDirect-ODBC-Critical-Security-
Bulletin-November-2022-CVE-2022-41853
Enhancements
------------
* The product package now includes .pdb files. These files contain debugging
symbols that can be used for diagnosing and debugging issues in the driver.
* The driver has been enhanced to optimize the handling of delete operations.
As part of this change:
- The driver no longer has an upper limit for how many rows can be deleted in
a single operation.
- The driver is significantly more efficient when removing all the rows in a
table, resulting in improved performance.
* The driver has been enhanced to support delete operations for very large
numbers of rows (exceeding 100 million). As a result of this change, the
performance has also been significantly improved when executing delete
operations. Note that this optimization applies only to unqualified delete
operations.
* 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.
* The driver has been enhanced to support the TLSv1.3 cryptographic protocol.
* The driver has been enhanced to allow you to configure whether the driver
inserts String values that exceed the column length defined in the relational
schema. You can configure this behavior using the new String Truncation
Method For Writes (StringTruncationMethodForWrites) options.
* The driver has been enhanced to allow you to increase the default length of
VARCHAR columns to increase the size of data values you can insert with the
driver. You can configure the new Min Varchar Size (MinVarcharSize) option to
specify minimum default length of fields mapped to VARCHAR.
* The driver has been enhanced to allow you to specify the format in which the
driver renders the MongoDB composite timestamp. This allows you to specify
the format of the MongoDB composite timestamp that is most appropriate for
your use case. You can configure this driver behavior using the new Timestamp
Format (TimestampFormat) option.
* The SQL engine server has been enhanced to automatically start and stop the
service as needed. When the new Broker mode is enabled (SQLEngineMode=3), the
SQL engine operates in an external Java process that is monitored by the
driver's Broker. The Broker eliminates the need to explicitly start and stop
the service, as well as more efficiently manage memory and resource consumption.
* The driver has been enhanced to support replacing the internal mapping files
at connection. When Create Map (CreateMap) is set to 1 (ForceNew), the driver
replaces the schema map files specified by the Schema Map (SchemaMap) option
with newly generated files at the same location. In addition, if you are
upgrading from driver version 8.0 to 8.1, the driver retains a copy of the
8.0 version of the schema map files as a backup when generating the 8.1
version of the files.
* 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.
* The driver has been enhanced to support data compression for all messages
passed between the client and server. Data compression can significantly
reduce network traffic, which, in turn, can lower data transfer costs for
cloud services. You can configure this feature with the new Network Message
Compressors (NetworkMessageCompressors) option.
Feature details:
- Available: Driver version 08.10.0157 (B1449, U1212, J000898)
* The driver has been enhanced to support MongoDB views created in the
database. MongoDB views are discovered during the sampling process
and mapped using the same schema format used for your collections.
Feature details:
- Available: Driver version 08.10.0131 (B1345, U1106, J000821)
- Proposed by the following DataDirect Idea:
https://progresssoftware.aha.io/ideas/ideas/DDIDEAS-I-356
* The driver has been upgraded to support the MongoDB Protocol using OP_MSG
opcode.
Feature details:
- Available: Driver version 08.10.0103 (B1198, U0950, J000776)
* The driver has been enhanced to support generating legacy virtual keys for
newly-discovered nested objects. For driver versions earlier than 8.1,
the driver used legacy virtual keys (unique identifiers) as a foreign key to
associate the child table back to the parent. When the Legacy
Virtual Keys (LegacyVirtualKeys) option is set to 1 (true), the driver
generates legacy virtual keys in the <object_name>_GENERATED_ID column in new
and migrated schemas. This functionality allows you to maintain consistent
column naming for driver generated virtual key columns when migrating
normalized schema maps from the 8.0 format.
Changed Behavior
----------------
* 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.
- To install the 32-bit drivers on 64-bit Windows platforms and start the SQL
engine service, the installer requires the 32-bit version of Java SE 11 or
higher installed on your machine and defined on your path.
* The behaviors of valid values for the Create Map (CreateMap) option have been
changed as follows:
- If set to 0 (No), the driver uses the current group of internal files
specified by the Schema Map option. If the files do not exist, the
connection fails.
- If set to 2 (NotExist), the driver uses the current group of internal files
specified by the Schema Map (SchemaMap) option. If the files do not exist,
the driver creates them.
Note: In the Configuration Manager help, the behavior for ordinal valid
values described in the Create Map description might be reversed in some
driver builds. Refer to the following documentation for the correct behavior
of this option:
https://docs.progress.com/bundle/datadirect-mongodb-odbc-81/
page/Create-Map.html
* The installer program has been updated to no longer install common components
for drivers that do not use them. As a result, the installer program no longer
installs the following common components for the MongoDB driver:
- OpenSSL library files, such as ivopenssl30.dll, ddopenssl30.dll, fips.dll,
and openssl.cnf.
- Curl library files, such as ivcurl28.dll and ddcurl28.dll.
If the files are not used by any other DataDirect driver on your machine, you
can safely remove them from existing product directories.
* The SchemaDefinition attribute has been added as an alias for the Schema Map
(SchemaMap) option. This change allows users to continue using their
configurations for earlier versions of the driver until they are able update
their connection settings. Note that SchemaDefinition is a deprecated attribute
and may not be supported in future versions of the driver.
Change details:
- Available: Driver version 08.10.0083 (B1145, U0894, J000647)
Changes for 8.1.0 GA
Enhancements
------------
* The driver has been enhanced to support the JavaScript and Regex data types.
* The normalization algorithm has been upgraded to improve sampling performance
and optimize the generation of tables in the relational view. In addition,
the new Schema Format (SchemaFormat) connection option allows you to
determine to which relational view the driver maps data, including
normalized, mixed, and flattened views.
* The driver supports migrating schema maps and internal files created with the
8.0 version of the driver so that they can be used by the 8.1 driver. By
migrating these files, you can continue to execute the same SQL statements
that you did with the 8.0 driver while still leveraging the advantages of the
8.1 driver.
* The driver has been enhanced to support LDAP (Lightweight Directory Access
Protocol) authentication.
* The new Schema Filter (SchemaFilter) connection option allows you to specify
the database and collections pairs for which you want the driver to fetch
metadata. Configuring this option can significantly improve connection times
by limiting the collections for which metadata is fetched to only those that
are required by your application.
* The new Qualify Normalized Names (QualifyNormalizedNames) option allows you
to determine whether names of relational child-tables normalized from arrays,
objects, subdocuments are prefixed with the collection name and names of any
parent objects.
* The new Special Char Behavior (SpecialCharBehavior) option allows you to
control how the driver handles the mapping of native identifiers
containing characters that would require them to be quoted in SQL statements.
This option provides a method to choose to continue using identifiers that
require quotation marks or for the driver to modify affected identifier names
so that quotation marks are not required.
* The new JSON columns (JSONColumns) option allows you to determine whether the
driver exposes complex columns as JSON values in addition to their normalized
mapping.
Note: Querying JSON values can be an expensive operation that could
negatively impact performance; therefore, you should only query JSON
values when necessary.
* The new Flatten Array Base (FlattenArrayBase) option allows you to specify
the starting ordinal value appended to column names for flattened arrays.
When flattening arrays, column names are appended with an underscore and the
ordinal value (<array_name>_<ordinal_location>). This option allows you to
determine whether the first ordinal value in the series is either a 0 or a
1.
* The driver has been enhanced to support replica set failover for write
operations. This feature can be enabled by specifying your replica set name
using the new Replica Set Name (ReplicaSetName) connection option.
* The driver has been enhanced to support connections to MongoDB Atlas clusters
using a DNS seed list. Instead of specifying connection information for
individual nodes, the driver allows you to specify the name of the DNS SRV
record using the Host Name (HostName) option. The driver then uses a DNS
lookup to discover the member nodes in the cluster to which it can connect.
You can control whether driver performs a DNS lookup using the new Enable
DNS Lookup (EnableDNSLookup) option.
* The driver now includes the MongoDB Configuration Manager for quick
configuration and testing of your driver in a web browser. The tool allows
you to:
- Configure data sources and connection strings
- Test connect your data sources and connection strings
- Execute SQL commands for testing
* The driver has been enhanced with the new Authentication Database
(AuthenticationDatabase) connection option, which provides a method to
specify the database in which the user id was created for user id and
password authentication (AuthenticationMethod=userIdPassword). This allows
you to explicitly select a set of credentials when the same user ID was
created on multiple databases.
* The driver has been enhanced to support the SCRAM-SHA-256 authentication
method for user ID and password authentication. When user ID and password
authentication is enabled (AuthenticationMethod=UserIDPassword), the driver
detects and uses the most secure method supported by the server.
* The driver has been enhanced to use proxy server settings defined in the
JVM system option by default. If no proxy settings are defined in the
connection string or data source, the driver will attempt to use the values
of the http.proxyHost and http.proxyPort JVM system option to connect to
the database.
* The driver has been enhanced to allow you to limit sampling to only new
collections when refreshing the schema map. This provides for quicker
processing times if you only want to map new collections or if existing
collections are unchanged. You can limit sampling to only new collections by
specifying the NEW option in a Refresh Map statement.
* The driver has been enhanced to support the native Decimal128 data type,
which maps to the Decimal ODBC type by default.
* The driver has added support for the MinKey and MaxKey special values.
* For base version B0649 and later, the driver has 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.
* The CAST_TO_NATIVE function escape has been introduced to select or insert a
value of a specific native type. This can be particularly useful when MongoDB
has inconsistent native types for a given field. Currently, CAST_TO_NATIVE
can only be used with the ObjectID type in SELECT statement filters and
literal INSERT values.
Changed behavior
----------------
* The default mapping behavior of the driver has been changed from generating a
normalized view of data to one that is a mixture of normalized and flattened
views. The mixed view reduces the number of tables generated while providing
a more intuitive data model. You can configure the mapping behavior using the
new Schema Format (SchemaFormat) option.
* The Schema Tool and manual customizations of the schema map are not currently
supported. However, you can modify schema using the mapping connection
options.
* The Create Database (CreateDB) connection option has been replaced by the
Create Map (CreateMap) option. The valid values and behavior are identical
for both options.
* The Database (Database) connection options has been replaced by the Database
Name (DatabaseName) option. The valid values and behavior are identical for
both options.
* The User Name (LogonID) connection option has been replaced with the User
(User) option. The valid values and behavior are identical for both options.
* The Config Options (ConfigOptions) connection options has been deprecated. As
a result, the driver has been enhanced to support setting each of the
configuration options formerly supported by Config Options as standalone
connection options.
* The following Config Options are no longer supported:
- DefaultVarcharSize
- MaxVarcharSize
- MinVarcharSize
To determine the default length of VARCHAR fields, the driver multiplies the
largest discovered field by 1.5. For example, if the largest detected field
has a length of 100 characters, the driver sets the default length to 150
characters.
DataDirect ODBC Driver Configuration Manager
The driver includes a browser-based configuration tool, the DataDirect ODBC
Driver Configuration Manager, that allows you to generate and test connection
URLs that you can use with your application. You can launch the Configuration
Manager by opening the ODBC Administrator from the Progress DataDirect
program group and creating or configuring a data source for the driver.
The Configuration Manager will open in your default web browser. For more
information, refer to the user's guide for your driver.
Notes, Known Problems, and Restrictions
The following are notes, known problems, and restrictions for the
8.1.0 release of the driver:
Crypto Protocol Version Values in Configuration Manager
-------------------------------------------------------
In the Configuration Manager, the connection option description for the Crypto
Protocol Version option fails to document TLSv1.3 as valid value. The valid values
for Crypto Protocol Version should be as follows:
TLSv1.3 | TLSv1.2 | TLSv1.1 | TLSv1 | SSLv3 | SSLv2
Out-of-Memory Errors
--------------------
When processing large sets of data, out-of-memory errors can occur when the size
of an intermediate result exceeds the available memory allocated to the JVM. If
you are encountering these errors, you can tune Fetch Size or Result Memory
Size to fit your environment.
* Reduce Fetch Size to reduce demands on the driver's internal memory. By
lowering the maximum number of rows as specified by Fetch Size, you lower the
number of rows the driver is required to process before returning data to the
application. Thus, you reduce demands on the driver's internal memory, and,
in turn, decrease the likelihood of out-of-memory errors.
* To tune Result Memory Size, decrease the value specified until results are
successfully returned. Intermediate results larger than the specified setting
will be written to disk as opposed to held in memory. When configured
correctly, this avoids memory limitations by not relying on memory to process
larger intermediate results. Be aware that while writing to disk reduces the
risk of out-of-memory errors, it also negatively impacts performance. For
optimal performance, decrease this value only to a size necessary to avoid
errors.
By default, Result Memory Size is set to -1, which sets the maximum
size of intermediate results held in memory to a percentage of the max Java
heap size. If you received errors using the default configuration, use the
max Java heap size divided by 4 as a starting point when tuning this option.
Write Operations When Connected to a Replica Set
------------------------------------------------
When connected to a replica set, you can execute Select, Insert, and Delete
against the primary node. However, you can only execute Select against
secondary nodes.
Mapped Columns with Numeric Names
---------------------------------
When accessing data from a mapped column with a numeric name, you must
enclose the column name in double quotes in the SQL statement. For example,
to select data from a column named 3, you submit the following statement:
SELECT "3" FROM <table>
Although numeric column names can be created a number of ways, they are
typically the result of normalizing a collection that contains array fields.
system.indexes Collection and Tables
------------------------------------
The driver hides the system.indexes collection. Internal tables, indicated by
names containing the "quot; character, are also hidden.
oplog.rs System Table
---------------------
The driver hides the oplog.rs system table.
Connection issues when specifying ExtendedOptions
-------------------------------------------------
When specifying a value for the Extended Options (ExtendedOptions) option in
the Configuration Manger, the driver currently adds the option and its value to
the Connection String field. However, the ExtendedOptions attribute is not
supported in Connection Strings; therefore, attempting to connect with the
generated connection string or executing a test connect with the configuration
manager will result in the an "Invalid attribute in the connection string: XO"
error.
To work around this issue, manually edit the connection string to remove
"ExtendedOptions=" from the connection string; then, specify the value of
ExtendOptions as semi-colon separated options in the string.
For example:
Driver=<driver_name>;HostName=<host_name>;ExtendedOptions=WorkArounds2=4096,
WorkArounds2=8192;
Becomes:
Driver=<driver_name>;HostName=<host_name>;WorkArounds2=4096;WorkArounds2=8192;
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 might be 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.
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 User's Guide for a description
of these options.
Documentation
PROGRESS DATADIRECT FOR ODBC FOR MONGDB DOCUMENTATION SET
---------------------------------------------------------
The driver documentation set is available from the Progress Information Hub:
https://docs.progress.com/category/datadirect-mongodb
You can access the online help system directly in either of the following ways.
* Via the HTML redirect in the installation Help directory
* By selecting Help from the information menu (? button) in the Configuration
Manager
Installed Files for 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 32-bit drivers on 64-bit machines:
C:\Program Files (x86)\Progress\DataDirect\ODBC\:
For all other installations:
C:\Program Files\Progress\DataDirect\ODBC\:
\<install_dir>\:
----------------
license.txt Progress DataDirect license agreement
\drivers:
---------
ivmongodb81.dll DataDirect MongoDB driver
ivmongodb81.pdb Debugging symbols for DataDirect
MongoDB driver
ivmongodb81r.dll DataDirect MongoDB driver resource file
ivicu.dll Unicode conversion tables
ivicu.pdb Debugging symbols for ICU library
IVODBC.LIC DataDirect License File
ivtrc28.dll DataDirect trace library
ivtrc28.pdb Debugging symbols for DataDirect trace library
qesqlext.h Header file for DataDirect-specific
ODBC Definitions
\FIXES:
-------
fixes8.0.txt List of fixes since last release
\help\:
-------
*.html HTML redirects to online connector help systems
and documentation resources
\install\:
---------
*.* Files associated with the installer program
\java\lib\:
-----------
mongodb.jar Java components for the driver
\NOTICES\:
---------
ODBC for MongoDB
v8.1 notices.txt Third-party vendor license agreements
\READMES\:
---------
ODBC for MongoDB
v8.1 readme.txt This file
\samples\bulk\:
---------------
bulk.c Bulk example source
bulk.exe Bulk application
bulk.mak Bulk example make file
bulk.sln Bulk example solution file
bulk.vcproj Bulk example project file
ddlogging.properties Log configuration file for
the MongoDB driver
\samples\bulkstrm\:
------------------
bulk.cpp Bulk streaming example source
bulk.hpp Bulk streaming example header
bulk.rc Bulk streaming example resource file
bulkstreaming.sln Bulk streaming example solution file
bulkstreaming.vcproj Bulk streaming example project file
bulkstrm.exe Bulk streaming example application
bulkstrm.txt Bulk streaming description
ddlogging.properties Log configuration file for the
MongoDB driver
msgprintf.hpp Bulk streaming example header file
ProgressDataDirect.bmp
ProgressDataDirect.ico
winmain.cpp Bulk streaming example source file
\samples\example\:
------------------
ddlogging.properties Log configuration file for the
MongoDB driver
example.c Example source
Example.exe Example application
example.h Example header
Example.mak Example make file
Example.sln Example solution file
Example.vcproj Example project file
\samples\translat:
-----------------
LIBMAIN.C
README.TRN Translation Library example description
TRANSLAT.C Translation Library example source file
WINNT.MAK Translation Library example make file
\tools\:
--------
ddextwin.exe License Extender utility
ddprocinfo.exe Processor Information utility
DSNConverterSil.exe Data Source Converter utility
mongodbserver32.exe The MongoDB driver SQL
Server Engine
XMLP.exe A GUI demo tool that persists a result set to
an XML data file
\tools\Power BI:
----------------
DataDirectMongoDB.pqx MongoDB Power BI connector file
install.bat Batch file to install Power BI connectors
\tools\Tableau\:
----------------
DataDirect MongoDB.tdc Tableau data source file
\uninstall\:
------------
*.* Files used to uninstall the product
Installed Files for the 64-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:
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\:
\<install_dir>\:
----------------
license.txt Progress DataDirect license agreement
\drivers\:
----------
ddmongodb81.dll DataDirect MongoDB driver
ddmongodb81.pdb Debugging symbols for DataDirect
MongoDB driver
ddmongodb81r.dll DataDirect MongoDB driver resource file
ddicu.dll Unicode conversion tables
ddicu.pdb Debugging symbols for ICU library
DDODBC.LIC DataDirect License File
ddtrc28.dll DataDirect trace library
ddtrc28.pdb Debugging symbols for DataDirect trace library
qesqlext.h Header file for DataDirect-specific ODBC
Definitions
\FIXES:
-------
fixes8.0.txt List of fixes since last release
\help\:
-------
*.html HTML redirects to online connector help systems
and documentation resources
\install\:
---------
*.* Files associated with the installer program
\java\lib\:
-----------
mongodb.jar Java components for the driver
\NOTICES\:
----------
ODBC for MongoDB
v8.1 notices.txt Third-party vendor license agreements
\READMES\:
----------
ODBC for MongoDB
v8.1 readme.txt This file
\samples\bulk\:
---------------
bulk.c Bulk example source
bulk.exe Bulk application
bulk.mak Bulk example make file
bulk.sln Bulk example solution file
bulk.vcproj Bulk example project file
ddlogging.properties Log configuration file for
the MongoDB driver
\samples\bulkstrm\:
------------------
bulk.cpp Bulk streaming example source
bulk.hpp Bulk streaming example header
bulk.rc Bulk streaming example resource file
bulkstreaming.sln Bulk streaming example solution file
bulkstreaming.vcproj Bulk streaming example project file
bulkstrm.exe Bulk streaming example application
bulkstrm.txt Bulk streaming description
ddlogging.properties Log configuration file for the
MongoDB driver
msgprintf.hpp Bulk streaming example header file
ProgressDataDirect.bmp
ProgressDataDirect.ico
winmain.cpp Bulk streaming example source file
\samples\example\:
------------------
ddlogging.properties Log configuration file for the
MongoDB driver
example.c Example source
Example.exe Example application
example.h Example header
Example.mak Example make file
Example.sln Example solution file
Example.vcproj Example project file
\samples\translat:
-----------------
LIBMAIN.C
README.TRN Translation Library example description
TRANSLAT.C Translation Library example source file
WINNT.MAK Translation Library example make file
\tools\:
-------
ddextwin.exe License Extender utility
ddprocinfo.exe Processor Information utility
DSNConverterSil.exe Data Source Converter utility
mongodbserver64.exe The MongoDB driver SQL Server Engine
XMLP.exe A GUI demo tool that persists a result set to
an XML data file
\tools\Power BI:
----------------
DataDirectMongoDB.pqx MongoDB Power BI connector file
install.bat Batch file to install Power BI connectors
\tools\Tableau\:
----------------
DataDirect MongoDB.tdc Tableau data source file
\uninstall\:
------------
*.* Files used to uninstall the product
~~~~~~~~~~~~~~~~~
February 2026
End of README.TXT