This guide walks you through everything you need to get started with the CData ODBC Driver for HubDB. You'll learn how to install and license the driver, configure your first connection, and explore next steps for working with HubDB data in your applications.
Installation & Licensing
System Requirements
- Windows: Windows 10/11 or Windows Server 2016+
- Linux: Most modern distributions with UnixODBC
Installing the Driver
Windows Installation
- Download the ODBC driver installer from your CData account or the evaluation download page.
- Run the installer and follow the installation wizard.
- The installer will guide you through the setup process and automatically register the driver with the system.
- As part of the installation process, you will be prompted to input the license key in order to activate your license. You should have received your license key via email from the CData Orders Team. The license key looks like this:
XXXX-XXXX-XXXX-XXXX-XXXX.
- Note: If you are running a trial, just select the Trial Key option.
- Both 32-bit and 64-bit drivers are included. Install both if you use applications with different architectures.
Linux Installation
- Ensure UnixODBC is installed:
sudo apt-get install unixodbc unixodbc-dev (Debian/Ubuntu)
sudo yum install unixODBC unixODBC-devel (RHEL/CentOS)
- Extract the driver package to /opt/cdata/
- The driver will be automatically registered in /etc/odbcinst.ini
Activating Your License
You should have received your license key via email from the CData Orders Team. The license key looks like this:
XXXX-XXXX-XXXX-XXXX-XXXX
Windows License Activation
Your license would typically be activated during installation. However, there are cases where you may need to activate it manually. The steps below walk you through manual activation:
- Open the ODBC driver application from the Start menu.
- Navigate to Help > Licensing
- Enter your license key in the provided field.
- Click Activate
- You should see "Licensed" status confirming successful activation.
Linux License Activation
- Navigate to the installation directory where you extracted the driver package. (i.e.cd /opt/cdata/cdata-odbc-driver-for-acumatica/bin/)
- Create a license file by running the following command sudo ./install-license.sh
- Replace with your actual license key.
- To activate a trial, omit the input.
Common Licensing Questions
Can I use my license on multiple machines?
Yes, depending on your subscription tier. Check your order confirmation or contact your account representative for details. If you are unsure of who your account representative is, contact [email protected].
I lost my license key. How do I retrieve it?
Email [email protected] with your order number, and we'll resend your license key.
Can I transfer my license to a different machine?
Yes. When transferring the license to a different machine, you will need to submit a License Transfer Request on our site linked below:
https://www.cdata.com/lic/transfer/
After the License Transfer Request is submitted and successfully processed, an activation will be added to your Product Key and you will be able to activate the full license on the other machine. Once this process is finished, the license on the previous machine will be invalid.
For additional licensing questions, contact [email protected]. Viewing and upgrading your license can now be done through our self-service portal at portal.cdata.com.
Connection Configuration
Once your driver is installed and licensed, you're ready to configure a connection to HubDB. The ODBC driver uses a DSN (Data Source Name) to store connection properties.
Creating a DSN
Windows: Using ODBC Data Source Administrator
- Open the ODBC Data Source Administrator (64-bit)
Note: Use the 64-bit version for 64-bit applications and the 32-bit version for 32-bit applications.
- Search for "ODBC" in the Windows Start menu
- Or navigate to: Control Panel > Administrative Tools > ODBC Data Sources
- Click the System DSN or User DSN tab
- System DSN: Available to all users on the machine (recommended for services)
- User DSN: Available only to the current user
- Select CData ODBC Driver for HubDB from the list, or click Add to create a new data source.
- Click OK or Finish to open the connection configuration dialog.
👁 Creating a DSN in Windows ODBC Administrator
Linux: Editing Config Files (odbcinst.ini & odbc.ini)
- Register the Driver by adding the section below to the odbcinst.ini file.
[CData ODBC Driver for HubDB]
Driver=/opt/cdata/cdata-odbc-driver-for-hubdb/lib/libhubdbodbc.x64.so
Description=CData ODBC Driver for HubDB
- Save the file.
- Create the DSN by adding the entry below to the odbc.ini file:
[CData HubDB Source]
Driver=/opt/cdata/cdata-odbc-driver-for-hubdb/lib/libhubdbodbc.x64.so
ConnectionProperty1=Value1
ConnectionProperty2=Value2
AuthScheme = OAuth
OAuthClientID = MyOAuthClientID
OAuthClientSecret = MyOAuthClientSecret
CallbackURL = http://localhost:33333
InitiateOAuth = GETANDREFRESH
- Save the file.
Configuring Connection Properties
There are two authentication methods available for connecting to HubDB data source: OAuth Authentication with a public HubSpot application and authentication with a Private application token.
Using a Custom OAuth App
AuthScheme must be set to "OAuth" in all OAuth flows. Be sure to review the Help documentation for the required connection properties for you specific authentication needs (desktop applications, web applications, and headless machines).
Follow the steps below to register an application and obtain the OAuth client credentials:
- Log into your HubSpot app developer account.
- Note that it must be an app developer account. Standard HubSpot accounts cannot create public apps.
- On the developer account home page, click the Apps tab.
- Click Create app.
- On the App info tab, enter and optionally modify values that are displayed to users when they connect. These values include the public application name, application logo, and a description of the application.
- On the Auth tab, supply a callback URL in the "Redirect URLs" box.
- If you're creating a desktop application, set this to a locally accessible URL like http://localhost:33333.
- If you are creating a Web application, set this to a trusted URL where you want users to be redirected to when they authorize your application.
- Click Create App. HubSpot then generates the application, along with its associated credentials.
- On the Auth tab, note the Client ID and Client secret. You will use these later to configure the driver.
Under Scopes, select any scopes you need for your application's intended functionality.
A minimum of the following scopes is required to access tables:
- hubdb
- oauth
- crm.objects.owners.read
- Click Save changes.
- Install the application into a production portal with access to the features that are required by the integration.
- Under "Install URL (OAuth)", click Copy full URL to copy the installation URL for your application.
- Navigate to the copied link in your browser. Select a standard account in which to install the application.
- Click Connect app. You can close the resulting tab.
Using a Private App
To connect using a HubSpot private application token, set the AuthScheme property to "PrivateApp."
You can generate a private application token by following the steps below:
- In your HubDB account, click the settings icon (the gear) in the main navigation bar.
- In the left sidebar menu, navigate to Integrations > Private Apps.
- Click Create private app.
- On the Basic Info tab, configure the details of your application (name, logo, and description).
- On the Scopes tab, select Read or Write for each scope you want your private application to be able to access.
- A minimum of hubdb and crm.objects.owners.read is required to access tables.
- After you are done configuring your application, click Create app in the top right.
- Review the info about your application's access token, click Continue creating, and then Show token.
- Click Copy to copy the private application token.
To connect, set PrivateAppToken to the private application token you retrieved.
Testing Your Connection
- After entering your connection properties, click Test Connection.
- A successful test confirms:
- Authentication credentials are correct.
- Network connectivity is established.
- Required permissions are in place.
- If the test fails, the error message will indicate what needs to be corrected.
- Click OK to save your DSN.
Common Connection Issues
Authentication Failed
Solution: Verify your credentials are current. For OAuth applications, you may need to authorize CData in your application's security settings. Contact [email protected] for authorization assistance.
Cannot Reach Server
Solution: Check firewall & proxy settings. Contact [email protected] for specific port requirements.
Table Not Found
Solution: Verify database and schema names. Use the Data Model tab in the DSN configuration to browse available tables.
Driver Not Found (Linux)
Solution: Verify the driver is correctly registered in odbcinst.ini. Contact [email protected] for further assistance.
For additional connection troubleshooting, contact [email protected] with your specific error message.
What's Next
Now that you have installed, licensed, and configured the driver, here are some scenarios you can use to explore our ODBC Drivers:
Get Support
If you need assistance at any point:
FAQs
Installation & Licensing
- Do I need administrator rights to install the driver?
Yes, administrator rights are required for system-wide installation on Windows and Linux.
- Can I install both 32-bit and 64-bit drivers on the same machine?
Yes, both versions are installed by default.
Connecting
Performance & Troubleshooting
General
- Where can I find the complete list of supported SQL operations?
Refer to the SQL Compliance chapter in the help documentation for complete SQL reference.
- How often is the driver updated?
CData releases major version updates for our drivers annually. Check your account portal or contact [email protected] for the latest version.
- Where can I find code examples for my programming language?
Check the Using ODBC section of the help documentation for language-specific examples (Python, PHP, C#, etc.).
For questions not covered in this FAQ, contact [email protected].