Connect to Atlas SQL with ODBC Driver
This page describes how to install and configure the MongoDB ODBC driver for connecting to a federated database instance.
Currently, the ODBC driver is available for the following architectures:
Windows
Ubuntu 22.04 (x86_64)
Supported Authentication Mechanisms
You can authenticate with SCRAM-SHA-1, SCRAM-SHA-256, MONGODB-X509, and MongoDB Passwordless Authentication with AWS.
Prerequisites
An Atlas account with a deployed cluster and Atlas Data Federation.
To learn more, see Get Started with Atlas Data Federation.
A federated database instance mapped to one or more data stores.
Note
If some or all of your data comes from an Atlas cluster, you must use MongoDB version 5.0 or greater for that cluster to take advantage of Atlas SQL.
An application or BI tool that you want to connect to your federated database instance with the ODBC driver.
Microsoft Visual C++ Redistributable 17.0 or higher for installing Microsoft C and C++ (MSVC) runtime libraries.
Note
If the C++ runtime libraries are not installed, the ODBC driver returns the following error:
The specified module could not be found (path of the dll which exists and has the proper permission).
An Atlas account with a deployed cluster and Atlas Data Federation.
To learn more, see Get Started with Atlas Data Federation.
A federated database instance mapped to one or more data stores.
Note
If some or all of your data comes from an Atlas cluster, you must use MongoDB version 5.0 or greater for that cluster to take advantage of Atlas SQL.
An application or BI tool that you want to connect to your federated database instance with the ODBC driver.
Microsoft Visual C++ Redistributable 17.0 or higher for installing Microsoft C and C++ (MSVC) runtime libraries.
Note
If the C++ runtime libraries are not installed, the ODBC driver returns the following error:
The specified module could not be found (path of the dll which exists and has the proper permission).
Procedure
You can use the ODBC driver to connect to SQL-based tools that accept an ODBC API.
Download the ODBC Driver
Download the latest MongoDB ODBC Driver version from the MongoDB download center.
Verify the integrity of the downloaded package.
The MongoDB release team digitally signs all software packages to certify that a particular MongoDB package is a valid and unaltered MongoDB release. Complete the following steps to verify the ODBC driver binary against its SHA256 key:
Download the
.sha256
file for Windows x64 from the MongoDB ODBC Drivers Downloads page.Compare the signature file to the MongoDB installer hash using the following Powershell script:
sigHash = (Get-Content $Env:HomePath\Downloads\mongodbodbc.msi.sha256 | Out-String). SubString(0,64).ToUpper(); ` fileHash = (Get-FileHash $Env:HomePath\Downloads\mongodbodbc.msi).Hash.Trim(); ` echo $sigHash; echo $fileHash; ` sigHash -eq $fileHash The command outputs three lines:
A SHA256 hash that you downloaded directly from MongoDB.
A SHA256 hash computed from the MongoDB ODBC driver binary you downloaded from MongoDB.
A True or False result depending if the hashes match.
If the hashes match, the MongoDB binary is verified.
Install and Configure the ODBC Driver
Configure a System DSN.
To configure your ODBC connection:
Open your ODBC Data Source Administrator.
Note
If you use a 64-bit processor, be sure to open the 64-bit ODBC Data Source Administrator.
Navigate to the System DSN tab.
Add a new System DSN.
When prompted to select a driver for your data source, select the MongoDB Atlas SQL ODBC Driver.
Enter your connection information. You must enter:
Note
You can get your connection information from the Connect using the Atlas SQL Interface modal.
FieldDescriptionDSNA name for your new DSN.UsernameA database username to use to connect to your database.PasswordThe database user's password.MongoDB URIYour MongoDB deployment URI.DatabaseThe name of the database to which to connect.Enable maximumCheckbox to enforce maximum string length of 4000 characters. You must enable this option to work with BI tools like Microsoft SQL Server Management Studio that can't support variable length string data with unknown maximum length.Once you enter the required connection information, you can test your connection with your ODBC Data Source Administrator.
Download and Verify the ODBC Driver
Download the MongoDB ODBC Driver.
Note
Click Copy link to save the URL you need to construct the download link for the signature file in a later step.
curl https://translators-connectors-releases.s3.amazonaws.com/mongosql-odbc-driver/ubuntu2204/1.4.0/release/mongoodbc.tar.gz --output mongoodbc.tar.gz
Verify the integrity of the downloaded package:
The MongoDB release team digitally signs all software packages to
certify that a particular MongoDB package is a valid and unaltered
MongoDB release. The atlas-sql-odbc.asc
key is available on
pgp.mongodb.com
Run the following command to download the
.sig
file.curl -LO https://translators-connectors-releases.s3.amazonaws.com/mongosql-odbc-driver/ubuntu2204/1.4.0/release/mongoodbc.tar.gz.sig Run the following command to download then import the key file.
curl -LO https://pgp.mongodb.com/atlas-sql-odbc.asc gpg --import atlas-sql-odbc.asc gpg: key 1CCF1A1263CDD699: public key "Atlas SQL ODBC Release Signing Key <packaging@mongodb.com>" imported gpg: Total number processed: 1 gpg: imported: 1 Run the following command to verify the MongoDB installation file.
gpg --verify mongoodbc.tar.gz.sig mongoodbc.tar.gz GPG should return this response:
gpg: Signature made Wed May 22 13:24:36 2024 MDT gpg: using RSA key 0C5F007ABC491E4A gpg: Good signature from "Atlas SQL ODBC Release Signing Key <packaging@mongodb.com>" [unknown] If the package is properly signed, but you do not currently trust the signing key in your local
trustdb
,gpg
will also return the following message:gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 1CF5 B0D7 B2F8 9E16 52D8 BA79 0C5F 007A BC49 1E4A If you receive the following error message, confirm that you imported the correct public key:
gpg: Can't check signature: public key not found
Extract the ODBC driver:
The following example extracts the archive contents to
/usr/local/lib/mongoodbc
. The mongoodbc
directory
contains a LICENSE
file, a README.MD
file, and a
bin
directory. The bin
directory contains the
libatsql.so
ODBC driver library.
sudo tar -zxf mongoodbc.tar.gz --directory /usr/local/lib
Install and Configure the ODBC Driver
Locate the ODBC driver configuration files.
Run the following command:
odbcinst -j Note the locations of the configuration files for the
DRIVERS
,SYSTEM DATA SOURCES
, andUSER DATA SOURCES
.Example:
unixODBC 2.3.9 DRIVERS............: /etc/odbcinst.ini SYSTEM DATA SOURCES: /etc/odbc.ini FILE DATA SOURCES..: /etc/ODBCDataSources USER DATA SOURCES..: /home/ubuntu/.odbc.ini SQLULEN Size.......: 8 SQLLEN Size........: 8 SQLSETPOSIROW Size.: 8
Configure the ODBC driver.
Open the
odbcinst.ini
file in your preferred editor.Example:
sudo vim /etc/odbcinst.ini Add the following entries to the file and specify the path to the
libatsql.so
ODBC driver library.Example:
[ODBC Drivers] MongoDB Atlas SQL ODBC Driver = Installed [MongoDB Atlas SQL ODBC Driver] Driver=/usr/local/lib/mongoodbc/bin/libatsql.so
Configure the System DSN or User DSN.
If multiple users share the DSN, configure the System DSN. If multiple users user shouldn't share the DSN, configure the User DSN. If a single user uses the DSN, you can configure the System DSN or User DSN.
Open the
SYSTEM DATA SOURCES
file orUSER DATA SOURCES
file in your preferred editor.System DSN Example:
sudo vim /etc/odbc.ini User DSN Example:
sudo vim /home/ubuntu/.odbc.ini Add the following entries to the file and specify the appropriate values.
Note
You can get your connection information from the Connect using the Atlas SQL Interface modal.
FieldDescriptionPassword
Database user's password.Driver
Path to thelibatsql.so
ODBC driver library.Database
Name of the database to which to connect.User
Database username to use to connect to your database.Uri
MongoDB deployment URI.UnicodeTranslationOption
Unicode encoding for Atlas SQL. Set toutf16
.enable_max_string_length
Optional. Flag to enforce maximum string length of 4000 characters. To enable, set value to1
and to disable, set value to0
. If omitted, defaults to0
. You must enable this option to work with BI tools like Microsoft SQL Server Management Studio that can't support variable length string data with unknown maximum length.Example:
[ODBC Data Sources] MongoDB_Atlas_SQL = "MongoDB Atlas SQL ODBC Driver" [MongoDB_Atlas_SQL] Password = your_password Driver = /usr/local/lib/mongoodbc/bin/libatsql.so Database = sample_mflix User = your_username Uri = mongodb://datalake.region.a.query.mongodb.net/?ssl=true UnicodeTranslationOption = utf16
Test your connection.
Run the following command:
iusql -v MongoDB_Atlas_SQL
The following example shows a successful connection:
+---------------------------------------+ | Connected! | | | | sql-statement | | help [tablename] | | quit | | | +---------------------------------------+
If the connection fails, verify the details in your configuration files against your Atlas Data Federation instance.
Note
The following warning doesn't impact the ODBC driver operation:
[MongoDB][API] Buffer size "0" not large enough for data.
The ODBC driver doesn't support the iusql
query
function.