MongoDB ODBC 8.1.0 UNIX
- 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)
UNIX and Linux 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.
***********************************************************************
This README file contains information for Progress(R) DataDirect(R)
for ODBC for MONGODB(TM).
This README file contains information not included in the PROGRESS
DATADIRECT(R) FOR ODBC FOR MONGODB(TM) DRIVER USER'S GUIDE.
CONTENTS
Post-GA Product Announcements
Requirements
Installation Directory
Data Source and Platform Support
Changes Since 8.1.0 GA
Changes for 8.1.0 GA
Configuring Data Sources
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).
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.
Also, you must set the library path environment variable of your operating
system to the directory containing your JVM's libjvm.so file and that
directory's parent directory.
* The driver requires the following runtime libraries:
- AIX: C/C++ runtime libraries version 16.1 or higher
- Linux: C/C++ runtime libraries version GCC 2.12 or higher
- Solaris: C/C++ runtime libraries version 12.6 or higher
Installation Directory
* The default installation directory for the 32-bit driver is:
/opt/Progress/DataDirect/ODBC
* The default installation directory for the 64-bit driver is:
/opt/Progress/DataDirect/ODBC_64Bit
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 driver binaries now include debugging symbols that can be used for
diagnosing and debugging issues in the driver.
* The ICU library files that are installed with the product have been upgraded
to version 74.1. As a part of this upgrade, the following platforms and their
file names have been updated:
- AIX platforms
- 32-bit driver: From libivicu28.a to libivicu.a
- 64-bit driver: From libddicu28.a to libddicu.a
Note - This upgrade is available starting in build 08.02.1072 of the ICU
library files.
- Linux platforms
- 32-bit driver: From libivicu28.so to libivicu.so
- 64-bit driver: From libddicu28.so to libddicu.so
Note - This upgrade is available starting in build 08.02.0965 of the ICU
library files.
- Solaris platforms (Sparc and Solaris X)
- 32-bit driver: From libivicu28.so to libivicu.so
- 64-bit driver: From libddicu28.so to libddicu.so
Note - This upgrade is available starting in build 08.02.1799 of the ICU
library files.
As part of the ICU 74.1 upgrade, the complier and runtime versions for the
driver have been changed to the following:
- For AIX platforms, the compiler version has been upgraded to xlclang++ 16.1.
As a result, you must have C/C++ runtime libraries of 16.1 or higher on
your machine.
- For Linux platforms, the compiler version has been upgraded to GCC 7.3.1.
As a result, you must have C/C++ runtime libraries of GCC 2.12 or higher
on your machine.
- For Solaris platforms, the compiler version has been upgraded to Oracle
Developer Studio 12.6. As a result, you must have C/C++ runtime libraries
of 12.6 or higher on your machine.
* 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 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 driver has been enhanced with the new Array Normalization Threshold
(ArrayNormalizationThreshold) connection option. Array Normalization
Threshold allows you to specify the length of arrays (in elements) at which
the driver begins to normalize arrays to child tables when generating a
flattened view. This provides you with a method to control the size and focus
of your parent table when encountering large arrays or nested arrays.
* 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.
* 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 product package no longer includes the ODBC Cursor library file
(odbccurs.so) because it has some known security vulnerabilities that
could potentially expose you to security risks.
Note: The installer program cannot remove the ODBC Cursor library file
automatically while installing a new version of the driver. Remove it
manually.
* 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.so, ddopenssl30.so, fips.so,
and openssl.cnf.
- Curl library files, such as libivcurl28.so and libddcurl28.so.
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
determines 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>_<oridinal_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 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.
* 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.
* A Password Encryption Tool, called ddencpwd, is now included with the product
package. It encrypts passwords for secure handling in connection strings and
odbc.ini files. At connection, the driver decrypts these passwords and passes
them to the data source as required.
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 control certain aspects of relational data model
generated by the driver using 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 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.
* The driver does not currently support the IBM System z Linux platform.
Configuring Data Sources
Data sources are stored in the system information file (typically,
odbc.ini). This file can be edited using a text editor. For details on
configuring this file, see earlier versions of the PROGRESS DATADIRECT FOR ODBC
FOR MONGODB DRIVER USER'S GUIDE.
Notes, Known Problems, and Restrictions
The following are notes, known problems, and restrictions for the
8.1 release of the driver:
Out-of-memory Errors
--------------------
The driver has been designed to handle large result sets. However,
out-of-memory errors can still occur. The following items outline how to reduce
the likelihood of out-of-memory errors for your environment.
* Reduce Fetch Size (FetchSize) to reduce demands on memory. By lowering the
maximum number of rows as specified by Fetch Size, you lower the number of
rows the driver is required to fetch and process in memory before returning
data to the application. Thus, you reduce demands on memory and decrease the
likelihood of out-of-memory errors.
* Decrease Result Memory Size (ResultMemorySize) until results are successfully
returned. Intermediate results larger than the value specified 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.
* Increase the JVM heap size. By increasing the max Java heap size, you increase
the amount of data the driver can accumulate in memory and avoid
out-of-memory errors.
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.
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.
ODBC Development on UNIX and Linux Platforms
--------------------------------------------
All of the Release 7.1 Core Components (header files, etc.) needed for
development of ODBC applications on UNIX and Linux are installed into
the /include directory created by the product installer.
Please read the notices.txt file in the installation directory for
licensing information regarding the ODBC Core Components. Contact your
Progress DataDirect representative if you have any questions.
Developers using programming languages other than C++:
The DataDirect ODBC Driver Manager is a C++ shared library. The ODBC
Driver Manager can be used with any language that supports loading a
C++ shared library; however, if you are using a programming language
other than C++, you must take additional steps to ensure that the C++
libraries are initialized properly when loaded. If you are not using
C++, consult your compiler documentation for instructions on using C++
shared libraries with your application.
LANG Environment Setting on UNIX and Linux Platforms
----------------------------------------------------
A default installation of the product on UNIX and Linux assumes that
the value of the LANG environment setting is en_US. If your locale is
not set to en_US, the drivers may not return error messages properly.
In this case, you must create a symbolic link in the
<Install_Dir>/locale directory that has the same value as the LANG
environment setting. This link must point to the
<Install_Dir>/locale/en_US directory.
SQLDriverConnect
----------------
On UNIX, SQLDriverConnect should not use options other than SQL_DRIVER_NOPROMPT
unless your application implements its own login dialog.
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.
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.
Documentation
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 via the HTML redirect in the
installation Help directory.
Installed Files for the 32-bit Driver
This file list assumes a full installation of the 32-bit driver and
documentation.
The installer copies the following files and subdirectories to the
product installation directory, by default:
/opt/Progress/DataDirect/ODBC:
/<install_dir>/:
----------------
odbc.csh Setup script for C shell
odbc.ini Sample odbc.ini file
odbcinst.ini Sample odbcinst.ini file
odbc.sh Setup script for Bourne shell
IVODBC.LIC DataDirect license file
license.txt End User License Agreement
/bin/:
------
ivtestlib Test application to check that required
libraries are present and loadable
/FIXES/:
--------
fixes8.0.txt List of fixes since last release
/help/:
-------
*.html HTML redirects to driver help systems
/include/:
----------
odbcinst.h Include files
qesqlext.h
sql.h
sqlext.h
sqltypes.h
sqlucode.h
sqlunx.h
/install/:
---------
*.* Files associated with the installer program
/java/lib/:
----------
mongodb.jar Java components of the driver
/lib/:
------
ivmongodb81.so DataDirect MongoDB driver
ivtrc28.so DataDirect trace library
libivicu.a Unicode conversion tables for AIX platforms
libivicu.so Unicode conversion tables for Linux and
Solaris platforms
libodbc.so ODBC Driver Manager [.a on AIX]
libodbcinst.so ODBC Installer [.a on AIX]
/locale/en_US/LC_MESSAGES/:
--------------------------
ivmongodb81.mo MongoDB driver message file
ivmongodb81.po MongoDB driver message file source
odbc.m ODBC Driver Manager message file
odbc.po ODBC Driver Manager message source
/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 Bulk application
bulk.c Bulk example source
bulk.mak Bulk example make file
bulk.txt Bulk load example readme
ddlogging.properties Log configuration file for the
MongoDB driver
/samples/bulkstrm/:
------------------
bulkstrm Bulk streaming example application
bulk.cpp Bulk streaming example source
bulk.hpp Bulk streaming example header
bulkstrm.txt Bulk streaming description
ddlogging.properties Log configuration file for the
MongoDB driver
main.cpp Bulk streaming example source file
msgprintf.hpp Bulk streaming example header file
streambulk.mak Bulk streaming example make file
/samples/example/:
------------------
example Example application
example.c Example source
example.h Example header
example.mak Example make file
ddlogging.properties Log configuration file for the
MongoDB driver
/samples/trn/:
--------------
makefile Translation Library example make file
readme.trn Translation Library example description
translat.c Translation Library example source file
/tools/:
--------
ddencpwd Password Encryption Tool
ddextu License Extender utility
ddprocinfo Processor Information utility
launch_server.sh Script that launches the SQL Engine in
server mode
/uninstall/:
------------
*.* Files used to uninstall the product
Installed Files for the 64-bit Driver
This file list assumes a full installation of the 64-bit driver and
documentation.
The installer copies the following files and subdirectories to the
product installation directory, by default:
/opt/Progress/DataDirect/ODBC_64Bit:
/<install_dir>/:
-------------
odbc.csh Setup script for C shell
odbc.ini Sample odbc.ini file
odbcinst.ini Sample odbcinst.ini file
odbc.sh Setup script for Bourne shell
DDODBC.LIC DataDirect license file
license.txt End User License Agreement
/bin/:
------
ddtestlib Test application to check that required
libraries are present and loadable
/FIXES/:
--------
fixes8.0.txt List of fixes since last release
/help/:
-------
*.html HTML redirects to driver help systems
/include/:
----------
odbcinst.h Include files
qesqlext.h
sql.h
sqlext.h
sqltypes.h
sqlucode.h
sqlunx.h
/install/:
---------
*.* Files associated with the installer program
/java/lib/:
----------
mongodb.jar Java components of the driver
/lib/:
------
ddmongodb81.so DataDirect MongoDB driver
ddtrc28.so DataDirect trace library
libddicu.a Unicode conversion tables for AIX platforms
libddicu.so Unicode conversion tables for Linux and Solaris
platforms
libodbc.so ODBC Driver Manager [.a on AIX]
libodbcinst.so ODBC Installer [.a on AIX]
/locale/en_US/LC_MESSAGES/:
---------------------------
ddmongodb81.mo MongoDB driver message file
ddmongodb81.po MongoDB driver message file source
odbc.m ODBC Driver Manager message file
odbc.po ODBC Driver Manager message source
/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 Bulk application
bulk.c Bulk example source
bulk.mak Bulk example make file
bulk.txt Bulk load example readme
ddlogging.properties Log configuration file for the
MongoDB driver
/samples/bulkstrm/:
------------------
bulkstrm Bulk streaming example application
bulk.cpp Bulk streaming example source
bulk.hpp Bulk streaming example header
bulkstrm.txt Bulk streaming description
ddlogging.properties Log configuration file for the
MongoDB driver
main.cpp Bulk streaming example source file
msgprintf.hpp Bulk streaming example header file
streambulk.mak Bulk streaming example make file
/samples/example/:
------------------
example Example application
example.c Example source
example.h Example header
example.mak Example make file
ddlogging.properties Log configuration file for the
MongoDB driver
/samples/trn/:
--------------
makefile Translation Library example make file
readme.trn Translation Library example description
translat.c Translation Library example source file
/tools/:
--------
ddencpwd Password Encryption Tool
ddextu License Extender utility
ddprocinfo Processor Information utility
launch_server.sh Script that launches the SQL Engine in
server mode
/uninstall/:
------------
*.* Files used to uninstall the product
~~~~~~~~~~~~~~~~~
February 2026
End of README.TXT