Connect to HubDB Data as a SQL Server Linked Server

SQL Server Linked Servers enable the SQL Server Database Engine to read data from remote data sources and execute commands against the remote database servers outside of the instance of SQL Server. Typically, linked servers are configured to enable the execution of a T-SQL statement that includes tables in another instance of SQL Server, or another database product such as Oracle. When paired with CData Connect AI, linked servers provides instant access to HubDB data from your SQL Server database. This article demonstrates how to connect to HubDB using Connect AI and query HubDB data in SQL Server Management Studio (SSMS).

CData Connect AI provides a pure SQL Server interface for HubDB, allowing you to query data from HubDB without replicating the data to a natively supported database. Using optimized data processing out of the box, CData Connect AI pushes all supported SQL operations (filters, JOINs, etc.) directly to HubDB, leveraging server-side processing to return the requested HubDB data quickly.

Configure HubDB Connectivity for SQL Server

Connectivity to HubDB from SQL Linked Servers is made possible through CData Connect AI. To work with HubDB data from SQL Linked Servers, we start by creating and configuring a HubDB connection.

1. Log into Connect AI, click Sources, and then click Add Connection

2. Select "HubDB" from the Add Connection panel

3. Enter the necessary authentication properties to connect to HubDB.

   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:

   1. Log into your HubSpot app developer account.
      • Note that it must be an app developer account. Standard HubSpot accounts cannot create public apps.
   2. On the developer account home page, click the Apps tab.
   3. Click Create app.
   4. 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.
   5. 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.
   6. Click Create App. HubSpot then generates the application, along with its associated credentials.
   7. On the Auth tab, note the Client ID and Client secret. You will use these later to configure the driver.

   8. 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
   9. Click Save changes.
   10. 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:

   1. In your HubDB account, click the settings icon (the gear) in the main navigation bar.
   2. In the left sidebar menu, navigate to Integrations > Private Apps.
   3. Click Create private app.
   4. On the Basic Info tab, configure the details of your application (name, logo, and description).
   5. On the Scopes tab, select Read or Write for each scope you want your private application to be able to access.
   6. A minimum of hubdb and crm.objects.owners.read is required to access tables.
   7. After you are done configuring your application, click Create app in the top right.
   8. Review the info about your application's access token, click Continue creating, and then Show token.
   9. Click Copy to copy the private application token.

   To connect, set PrivateAppToken to the private application token you retrieved.

   
4. Click Save & Test
5. Navigate to the Permissions tab in the Add HubDB Connection page and update the User-based permissions.

Add a Personal Access Token

When connecting to Connect AI through the REST API, the OData API, or the Virtual SQL Server, a Personal Access Token (PAT) is used to authenticate the connection to Connect AI. It is best practice to create a separate PAT for each service to maintain granularity of access.

1. Click on the Gear icon () at the top right of the Connect AI app to open the settings page.
2. On the Settings page, go to the Access Tokens section and click Create PAT.
3. Give the PAT a name and click Create.
4. The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.

With the connection configured and a PAT generated, you are ready to connect to HubDB data from .

Connect to HubDB from SQL Server using Connect AI

To establish a connection from SQL Server Linked Server to the CData Connect AI Virtual SQL Server API, follow these steps.

1. Open Microsoft SQL Server Management Studio.
2. In the Object Explorer pane, open Server Objects, right-click Linked Servers, and select New Linked Server.

3. The New Linked Server dialogue opens. On the General page, enter the following information:
   • Enter a name for the server in the Linked server field.
   • Select the radio button Other data source and select SQL Server Native Client 11.0 as the provider.
   • In the Data source field, enter tds.cdata.com,14333
   • In the Catalog field, enter enter the Connection Name of the CData Connect AI data source you want to connect to (for example, HubDB1).
   
4. Select the Security page. At the bottom, select the radio button labeled Be made using this security context and enter the following information:
   • Remote login - enter your CData Connect AI username. This is displayed in the top-right corner of the CData Connect AI interface. For example, [email protected].
   • With password - enter the PAT you generated on the Settings page.
   
5. Click OK to create the server.
Your linked server can now be used to access the data in the data source you specified. If you need to access data from more sources, create another linked server for each one.

Execute Queries

You can now execute queries to the HubDB linked server from any tool that can connect to SQL Server. An example SQL query would be:

		SELECT * FROM [CDATA CONNECT CLOUD].[HubDB1].[HubDB].[NorthwindProducts]
	

We have successfully created a linked server that allows us to query HubDB data.

Get CData Connect AI

To get live data access to hundreds of SaaS, Big Data, and NoSQL sources directly from your SQL Server database, try CData Connect AI today!