How to connect PolyBase to Gumroad

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 API Driver for ODBC, you get access to your Gumroad data directly alongside your SQL Server data. This article describes creating an external data source and external tables to grant access to live Gumroad data using T-SQL queries.

NOTE: PolyBase is only available on SQL Server 19 and above.

The CData ODBC drivers offer unmatched performance for interacting with live Gumroad data using PolyBase due to optimized data processing built into the driver. When you issue complex SQL queries from SQL Server to Gumroad, the driver pushes down supported SQL operations, like filters and aggregations, directly to Gumroad and utilizes the embedded SQL engine to process unsupported operations (often SQL functions and JOIN operations) client-side. And with PolyBase, you can also join SQL Server data with Gumroad data, using a single query to pull data from distributed sources.

Connect to Gumroad

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs. To create an external data source in SQL Server using PolyBase, configure a System DSN (CData Gumroad Sys is created automatically).

Using OAuth Authentication

To authenticate to Gumroad and connect to your own data or to allow other users to connect to their data, you can use the OAuth 2.0 standard. This is the recommended authentication method.

First you need to register an OAuth application with Gumroad. You can create an OAuth application by visiting your Gumroad account settings at https://app.gumroad.com/settings/advanced and navigating to the Applications section.

After setting the following connection properties, you are ready to connect:

• AuthScheme: Set this to OAuth.
• InitiateOAuth: Set this to GETANDREFRESH. The CData API Profile for Gumroad will automatically walk through the OAuth process in order to obtain the access token.
• OAuthClientID: Set this to the client_id that is specified in your app settings.
• OAuthClientSecret: Set this to the client_secret that is specified in your app settings.
• CallbackURL: Set this to the Redirect URI you specified in your app settings.

Example connection string

Profile=C:\profiles\Gumroad.apip;AuthScheme=OAuth;InitiateOAuth=GETANDREFRESH;OAuthClientId=your_client_id;OAuthClientSecret=your_client_secret;CallbackUrl=your_callback_url;

Click "Test Connection" to ensure that the DSN is connected to Gumroad properly. Navigate to the Tables tab to review the table definitions for Gumroad.

Create an External Data Source for Gumroad Data

After configuring the connection, you need to create a master encryption key and a credential database for the external data source.

Creating a Master Encryption Key

Execute the following SQL command to create a new master key, 'ENCRYPTION,' to encrypt the credentials for the external data source.

CREATE MASTER KEY ENCRYPTION BY PASSWORD = 'password';

Creating a Credential Database

Execute the following SQL command to create credentials for the external data source connected to Gumroad data.

NOTE: Since Gumroad does not require a User or Password to authenticate, you may use whatever values you wish for IDENTITY and SECRET.

CREATE DATABASE SCOPED CREDENTIAL api_creds
WITH IDENTITY = 'username', SECRET = 'password';

Create an External Data Source for Gumroad

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

• Set the LOCATION parameter , using the DSN and credentials configured earlier.

For Gumroad, set SERVERNAME to the URL or address for your server (e.g. 'localhost' or '127.0.0.1' for local servers; the remote URL for remote servers). Leave PORT empty. PUSHDOWN is set to ON by default, meaning the ODBC Driver can leverage server-side processing for complex queries.

CREATE EXTERNAL DATA SOURCE cdata_api_source
WITH ( 
  LOCATION = 'odbc://SERVER_URL',
  CONNECTION_OPTIONS = 'DSN=CData Gumroad Sys',
  -- PUSHDOWN = ON | OFF,
  CREDENTIAL = api_creds
);

Create External Tables for Gumroad

After creating the external data source, use CREATE EXTERNAL TABLE statements to link to Gumroad data from your SQL Server instance. The table column definitions must match those exposed by the CData API Driver for ODBC. You can refer to the Tables tab of the DSN Configuration Wizard to see the table definition.

Sample CREATE TABLE Statement

The statement to create an external table based on a Gumroad CustomFields would look similar to the following:

CREATE EXTERNAL TABLE CustomFields(
   [nvarchar](255) NULL,
   [nvarchar](255) NULL,
  ...
) WITH ( 
  LOCATION='CustomFields',
  DATA_SOURCE=cdata_api_source
);

Having created external tables for Gumroad in your SQL Server instance, you are now able to query local and remote data simultaneously. Thanks to built-in query processing in the CData ODBC Driver, you know that as much query processing as possible is being pushed to Gumroad, freeing up local resources and computing power. Download a free, 30-day trial of the ODBC Driver for Gumroad and start working with live Gumroad data alongside your SQL Server data today.