Getting Started with the CData SSIS Components for HubDB
This guide explains everything you need to get started with the CData SSIS Components for HubDB. You'll learn how to install the components, activate your license, configure your first SSIS connection manager, and build a data flow task to move and transform HubDB data in your SQL Server Integration Services workflows.
Installation & Licensing
System Requirements
- Windows: Windows 10/11 or Windows Server 2016+
- Visual Studio: Visual Studio 2015 or later
- SQL Server: SQL Server 2014, 2016, 2017, 2019, or 2022
Installing the SSIS Components
- Download the SSIS Components installer for HubDB from your CData account or the evaluation download page
- Run the installer and follow the installation wizard
- The installer automatically registers the Connection Manager, Source, and Destination components with Visual Studio
- When prompted, activate your license using the product key sent to you by the CData Orders Team:
XXXX-XXXX-XXXX-XXXX-XXXX- Note: To run a trial, choose the Trial Key option.
Enabling SSIS in Visual Studio 2022
If you are using Visual Studio 2022, the SQL Server Integration Services Projects extension must be installed.
- In Visual Studio, select Extensions > Manage Extensions
- Search for SQL Server Integration Services Projects 2022
- Click Install
- Close Visual Studio and run the downloaded Microsoft.DataTools.IntegrationServices.exe installer
- Reopen Visual Studio. The Integration Services Project template will now appear when creating a new project
Activating Your License
During installation, you are prompted to activate the SSIS Component license. If you need to update or change activation:
License Activation
The installer automatically prompts you to add your license. During installation, you can choose to:
- Use your existing subscription license key, or
- Enter your trial license
To activate a full subscription license, contact the CData Orders Team and request your product key at [email protected].
Enter the license key in the installer when prompted. Once activated, the components will be licensed and ready to use inside Visual Studio without any additional steps.
Runtime Licensing
When deploying SSIS packages, a Runtime Key (RTK) can also be used:
- Set the RTK property in the Connection Manager before deployment
Common Licensing Questions
Can I use my license on multiple machines?
Yes, depending on your subscription tier. Contact [email protected] for details.
I lost my license key. How do I retrieve it?
Email [email protected] with your order number, and we'll resend your license key.
How do I transfer my license to another 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.
You may also view and upgrade licenses in the self-service portal at portal.cdata.com.
Connection Configuration
Once the components are installed and licensed, you can configure a connection to HubDB using an SSIS Connection Manager. This Connection Manager stores all authentication and connection properties used by the Source and Destination components.
Creating a Connection Manager
- In the bottom Connection Managers panel of your SSIS package, right-click and select New Connection
- Select CData SSIS Components for HubDB from the list
- Click Add to open the Connection Manager UI
- Enter the required authentication properties (OAuth, API token, client credentials, etc.) depending on your HubDB
- 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.
- 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.
- Click Test Connection to confirm connectivity
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:
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:
To connect, set PrivateAppToken to the private application token you retrieved.
Building an SSIS Data Flow
With a Connection Manager created, you can now pull data from HubDB or push data into it using SSIS data flow tasks.
Creating a Data Flow Task
- In the Control Flow tab, drag a Data Flow Task onto the design surface
- Double-click the task to open the Data Flow workspace
Using the Source Component
- In the SSIS Toolbox, drag the CData HubDB Source component into the Data Flow
- Double-click it to open the Source Editor
- Select the CData HubDB Connection Manager you created
- Choose a table or view to extract records from
- Click OK to save your configuration
Using the Destination Component
- Drag a SQL Server Destination onto the canvas
- Double-click it to open the Destination Editor
- Select an existing table or click New to auto-generate a table based on the Source schema
- Connect the Source output to the Destination input and map the columns as needed
- At this point you have created a data flow task for replicating your HubDB data to a SQL Server database
Testing Your Data Flow
- Return to the Control Flow tab
- Click Start Debugging
- Monitor the progress indicators
- Review row counts and ensure data is loading as expected
Common Connection Issues
Authentication Failed
Solution: Verify OAuth settings, client IDs, secrets, or token permissions for your HubDB. Contact [email protected] for OAuth troubleshooting.
Cannot Reach Server
Solution: Check firewall, proxy, and VPN configurations. Contact [email protected] for specific port requirements.
Table Not Found
Solution: Confirm you selected the correct schema or database when querying HubDB.
What's Next
Now that you have installed, licensed, and configured the SSIS Components, here are scenarios you can use to explore our SSIS tools:
| SSIS Component | Article Title |
|---|---|
| BIML | Use Biml to Build SSIS Tasks to Replicate HubDB to SQL Server |
| SSIS Export | Export Data from SQL Server to HubDB through SSIS |
| SSIS Import | Import HubDB Data into SQL Server using SSIS |
| SSIS Lookup | Insert New or Update Existing HubDB Records from SQL Server |
Get Support
If you need assistance at any point:
- Technical Support: [email protected]
- Community Forum: CData Community Site
- Help Documentation: Installed locally and available online
FAQs
Installation & Licensing
- Do I need administrator rights to install the SSIS Components?
Yes, administrator rights are required to install components for use across Visual Studio. - Do I need an RTK to deploy to Azure Data Factory?
Yes. Set the RTK property in the Connection Manager before publishing.
Connecting
- Can I use multiple HubDB accounts?
Create separate Connection Managers for each account. - Can I connect through a proxy?
Yes. Configure proxy settings in the Connection Manager properties. - How do I test my connection?
Click Test Connection in the Connection Manager UI.
Performance & Troubleshooting
- Why is my data flow slow?
Add filters, limit rows, and ensure batching settings are configured in the Source component. - How do I enable logging?
Add the following to your connection manager:- Logfile: /path/to/logfile.log
- Verbosity: 3
Be prepared to securely upload the log file upon request when reaching out to [email protected] for troubleshooting analysis.
For questions not covered in this FAQ, contact [email protected].