Model Context Protocol (MCP) finally gives AI models a way to access the business data needed to make them really useful at work. CData MCP Servers have the depth and performance to make sure AI has access to all of the answers.
Try them now for free →Connect to HCL Domino Data as an External Data Source using PolyBase
Use CData Connect Cloud and PolyBase to create an external data source in SQL Swerver with access to live HCL Domino data.
PolyBase for SQL Server allows you to query external data by using the same Transact-SQL syntax used to query a database table. When paired with the CData ODBC Driver for HCL Domino, you get access to your HCL Domino data directly alongside your SQL Server data. This article describes creating an external data source and external tables to grant access to live HCL Domino data using T-SQL queries.
NOTE: PolyBase is only available on SQL Server 19 and above, and only for Standard SQL Server.
CData Connect Cloud provides a pure SQL Server interface for HCL Domino, allowing you to query data from HCL Domino without replicating the data to a natively supported database. Using optimized data processing out of the box, CData Connect Cloud pushes all supported SQL operations (filters, JOINs, etc.) directly to HCL Domino, leveraging server-side processing to return the requested HCL Domino data quickly.
Configure HCL Domino Connectivity for PolyBase
Connectivity to HCL Domino from PolyBase is made possible through CData Connect Cloud. To work with HCL Domino data from PolyBase, we start by creating and configuring a HCL Domino connection.
- Log into Connect Cloud, click Connections and click Add Connection
- Select "HCL Domino" from the Add Connection panel
-
Enter the necessary authentication properties to connect to HCL Domino.
Connecting to Domino
To connect to Domino data, set the following properties:
- URL: The host name or IP of the server hosting the Domino database. Include the port of the server hosting the Domino database. For example: http://sampleserver:1234/
- DatabaseScope: The name of a scope in the Domino Web UI. The driver exposes forms and views for the schema governed by the specified scope. In the Domino Admin UI, select the Scopes menu in the sidebar. Set this property to the name of an existing scope.
Authenticating with Domino
Domino supports authenticating via login credentials or an Azure Active Directory OAuth application:
Login Credentials
To authenticate with login credentials, set the following properties:
- AuthScheme: Set this to "OAuthPassword"
- User: The username of the authenticating Domino user
- Password: The password associated with the authenticating Domino user
The driver uses the login credentials to automatically perform an OAuth token exchange.
AzureAD
This authentication method uses Azure Active Directory as an IdP to obtain a JWT token. You need to create a custom OAuth application in Azure Active Directory and configure it as an IdP. To do so, follow the instructions in the Help documentation. Then set the following properties:
- AuthScheme: Set this to "AzureAD"
- InitiateOAuth: Set this to GETANDREFRESH. You can use InitiateOAuth to avoid repeating the OAuth exchange and manually setting the OAuthAccessToken.
- OAuthClientId: The Client ID obtained when setting up the custom OAuth application.
- OAuthClientSecret: The Client secret obtained when setting up the custom OAuth application.
- CallbackURL: The redirect URI defined when you registered your app. For example: https://localhost:33333
- AzureTenant: The Microsoft Online tenant being used to access data. Supply either a value in the form companyname.microsoft.com or the tenant ID.
The tenant ID is the same as the directory ID shown in the Azure Portal's Azure Active Directory > Properties page.
- Click Create & Test
-
Navigate to the Permissions tab in the Add HCL Domino Connection page and update the User-based permissions.


Add a Personal Access Token
If you are connecting from a service, application, platform, or framework that does not support OAuth authentication, you can create a Personal Access Token (PAT) to use for authentication. Best practices would dictate that you create a separate PAT for each service, to maintain granularity of access.
- Click on your username at the top right of the Connect Cloud app and click User Profile.
- On the User Profile page, scroll down to the Personal Access Tokens section and click Create PAT.
- Give your PAT a name and click Create.
- The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.

Create an External Data Source for HCL Domino Data
After configuring the connection, you need to create a credential database for the external data source.
Creating a Credential Database
Execute the following SQL command to create credentials for the external data source connected to HCL Domino data.
NOTE: Set IDENTITY to your Connect Cloud username and set SECRET to your Personal Access Token.
CREATE DATABASE SCOPED CREDENTIAL ConnectCloudCredentials WITH IDENTITY = 'yourusername', SECRET = 'yourPAT';
Create an External Data Source for HCL Domino
Execute a CREATE EXTERNAL DATA SOURCE SQL command to create an external data source for HCL Domino with PolyBase:
CREATE EXTERNAL DATA SOURCE ConnectCloudInstance WITH ( LOCATION = 'sqlserver://tds.cdata.com:14333', PUSHDOWN = ON, CREDENTIAL = ConnectCloudCredentials );
Create External Tables for HCL Domino
After creating the external data source, use CREATE EXTERNAL TABLE statements to link to HCL Domino data from your SQL Server instance. The table column definitions must match those exposed by CData Connect Cloud. You can use the Data Explorer in Connect Cloud to see the table definition.

Sample CREATE TABLE Statement
Execute a CREATE EXTERNAL TABLE SQL command to create the external table(s), using the collation and setting the LOCATION to three-part notation for the connection, catalog, and table. The statement to create an external table based on a HCL Domino ByName would look similar to the following.
CREATE EXTERNAL TABLE ByName( Name COLLATE [nvarchar](255) NULL, Address COLLATE [nvarchar](255) NULL, ... ) WITH ( LOCATION='Domino1.Domino.ByName', DATA_SOURCE=ConnectCloudInstance );
Having created external tables for HCL Domino in your SQL Server instance, you are now able to query local and remote data simultaneously. To get live data access to 100+ SaaS, Big Data, and NoSQL sources directly from your SQL Server database, try CData Connect Cloud today!