![]() |
VOOZH | about |
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 Elasticsearch, you get access to your Elasticsearch data directly alongside your SQL Server data. This article describes creating an external data source and external tables to grant access to live Elasticsearch data using T-SQL queries.
NOTE: PolyBase is only available on SQL Server 19 and above.
CData Connect AI provides a pure SQL Server interface for Elasticsearch, allowing you to query data from Elasticsearch 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 Elasticsearch, leveraging server-side processing to return the requested Elasticsearch data quickly.
Accessing and integrating live data from Elasticsearch has never been easier with CData. Customers rely on CData connectivity to:
Users frequently integrate Elasticsearch data with analytics tools such as Crystal Reports, Power BI, and Excel, and leverage our tools to enable a single, federated access layer to all of their data sources, including Elasticsearch.
For more information on CData's Elasticsearch solutions, check out our Knowledge Base article: CData Elasticsearch Driver Features & Differentiators.
Connectivity to Elasticsearch from PolyBase is made possible through CData Connect AI. To work with Elasticsearch data from PolyBase, we start by creating and configuring a Elasticsearch connection.
Set the Server and Port connection properties to connect. To authenticate, set the User and Password properties, PKI (public key infrastructure) properties, or both. To use PKI, set the SSLClientCert, SSLClientCertType, SSLClientCertSubject, and SSLClientCertPassword properties.
The data provider uses X-Pack Security for TLS/SSL and authentication. To connect over TLS/SSL, prefix the Server value with 'https://'. Note: TLS/SSL and client authentication must be enabled on X-Pack to use PKI.
Once the data provider is connected, X-Pack will then perform user authentication and grant role permissions based on the realms you have configured.
๐ Configuring a connection (Salesforce is shown)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.
With the connection configured and a PAT generated, you are ready to connect to Elasticsearch data from Polybase.
After configuring the connection, you need to create a credential database for the external data source.
Execute the following SQL command to create credentials for the external data source connected to Elasticsearch data.
NOTE: Set IDENTITY to your Connect AI username and set SECRET to your Personal Access Token.
CREATE DATABASE SCOPED CREDENTIAL ConnectCloudCredentials WITH IDENTITY = 'yourusername', SECRET = 'yourPAT';
Execute a CREATE EXTERNAL DATA SOURCE SQL command to create an external data source for Elasticsearch with PolyBase:
CREATE EXTERNAL DATA SOURCE ConnectCloudInstance WITH ( LOCATION = 'sqlserver://tds.cdata.com:14333', PUSHDOWN = ON, CREDENTIAL = ConnectCloudCredentials );
After creating the external data source, use CREATE EXTERNAL TABLE statements to link to Elasticsearch data from your SQL Server instance. The table column definitions must match those exposed by CData Connect AI. You can use the Data Explorer in Connect AI to see the table definition.
๐ Table definition in the Data Explorer (Salesforce is shown)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 Elasticsearch Orders would look similar to the following.
CREATE EXTERNAL TABLE Orders( OrderName COLLATE [nvarchar](255) NULL, Freight COLLATE [nvarchar](255) NULL, ... ) WITH ( LOCATION='Elasticsearch1.Elasticsearch.Orders', DATA_SOURCE=ConnectCloudInstance );
Having created external tables for Elasticsearch in your SQL Server instance, you are now able to query local and remote data simultaneously. 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!
Learn more about CData Connect AI or sign up for free trial access:
Free Trial