![]() |
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 BigQuery, you get access to your BigQuery data directly alongside your SQL Server data. This article describes creating an external data source and external tables to grant access to live BigQuery 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 BigQuery, allowing you to query data from BigQuery 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 BigQuery, leveraging server-side processing to return the requested BigQuery data quickly.
CData simplifies access and integration of live Google BigQuery data. Our customers leverage CData connectivity to:
Most CData customers are using Google BigQuery as their data warehouse and so use CData solutions to migrate business data from separate sources into BigQuery for comprehensive analytics. Other customers use our connectivity to analyze and report on their Google BigQuery data, with many customers using both solutions.
For more details on how CData enhances your Google BigQuery experience, check out our blog post: https://www.cdata.com/blog/what-is-bigquery
Connectivity to BigQuery from PolyBase is made possible through CData Connect AI. To work with BigQuery data from PolyBase, we start by creating and configuring a BigQuery connection.
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 BigQuery 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 BigQuery 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 BigQuery 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 BigQuery 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 BigQuery Orders would look similar to the following.
CREATE EXTERNAL TABLE Orders( OrderName COLLATE [nvarchar](255) NULL, Freight COLLATE [nvarchar](255) NULL, ... ) WITH ( LOCATION='GoogleBigQuery1.GoogleBigQuery.Orders', DATA_SOURCE=ConnectCloudInstance );
Having created external tables for BigQuery 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