Connect to BigCommerce Data as an External Data Source using PolyBase

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 BigCommerce, you get access to your BigCommerce data directly alongside your SQL Server data. This article describes creating an external data source and external tables to grant access to live BigCommerce 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 BigCommerce, allowing you to query data from BigCommerce 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 BigCommerce, leveraging server-side processing to return the requested BigCommerce data quickly.

Configure BigCommerce Connectivity for PolyBase

Connectivity to BigCommerce from PolyBase is made possible through CData Connect Cloud. To work with BigCommerce data from PolyBase, we start by creating and configuring a BigCommerce connection.

1. Log into Connect Cloud, click Connections and click Add Connection
2. Select "BigCommerce" from the Add Connection panel
3. Enter the necessary authentication properties to connect to BigCommerce.

   BigCommerce authentication is based on the standard OAuth flow. To authenticate, you must initially create an app via the Big Commerce developer platform where you can obtain an OAuthClientId, OAuthClientSecret, and CallbackURL. These three parameters will be set as connection properties to your driver.

   Additionally, in order to connect to your BigCommerce Store, you will need your StoreId. To find your Store Id please follow these steps:

   1. Log in to your BigCommerce account.
   2. From the Home Page, select Advanced Settings > API Accounts.
   3. Click Create API Account.
   4. A text box named API Path will appear on your screen.
   5. Inside you can see a URL of the following structure: https://api.bigcommerce.com/stores/{Store Id}/v3.
   6. As demonstrated above, your Store Id will be between the 'stores/' and '/v3' path paramters.
   7. Once you have retrieved your Store Id you can either click Cancel or proceed in creating an API Account in case you do not have one already.
4. Click Create & Test
5. Navigate to the Permissions tab in the Add BigCommerce 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.

1. Click on your username at the top right of the Connect Cloud app and click User Profile.
2. On the User Profile page, scroll down to the Personal Access Tokens section and click Create PAT.
3. Give your 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.

Create an External Data Source for BigCommerce 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 BigCommerce 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 BigCommerce

Execute a CREATE EXTERNAL DATA SOURCE SQL command to create an external data source for BigCommerce with PolyBase:

CREATE EXTERNAL DATA SOURCE ConnectCloudInstance
WITH ( 
  LOCATION = 'sqlserver://tds.cdata.com:14333',
  PUSHDOWN = ON,
  CREDENTIAL = ConnectCloudCredentials
);

Create External Tables for BigCommerce

After creating the external data source, use CREATE EXTERNAL TABLE statements to link to BigCommerce 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 BigCommerce Customers would look similar to the following.

CREATE EXTERNAL TABLE Customers(
  FirstName COLLATE [nvarchar](255) NULL,
  LastName COLLATE [nvarchar](255) NULL,
  ...
) WITH ( 
  LOCATION='BigCommerce1.BigCommerce.Customers',
  DATA_SOURCE=ConnectCloudInstance
);

Having created external tables for BigCommerce 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!