How to connect PolyBase to Salesloft

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

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

The CData ODBC drivers offer unmatched performance for interacting with live Salesloft data using PolyBase due to optimized data processing built into the driver. When you issue complex SQL queries from SQL Server to Salesloft, the driver pushes down supported SQL operations, like filters and aggregations, directly to Salesloft 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 Salesloft data, using a single query to pull data from distributed sources.

Connect to Salesloft

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 Salesloft Sys is created automatically).

SalesLoft authenticates using the OAuth authentication standard or an API Key. OAuth requires the authenticating user to interact with SalesLoft using the browser.

Using OAuth

For OAuth authentication, create an OAuth app to obtain the OAuthClientId, OAuthClientSecret, and CallbackURL connection properties. See the OAuth section in the Help documentation for an authentication guide.

Using APIKey

Alternatively, you can authenticate with an APIKey. Provision an API key from the SalesLoft user interface: https://accounts.salesloft.com/oauth/applications/. You will receive a Key which will be used when issuing requests.

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

Create an External Data Source for Salesloft 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 Salesloft data.

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

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

Create an External Data Source for Salesloft

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

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

For Salesloft, 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_salesloft_source
WITH ( 
  LOCATION = 'odbc://SERVER_URL',
  CONNECTION_OPTIONS = 'DSN=CData Salesloft Sys',
  -- PUSHDOWN = ON | OFF,
  CREDENTIAL = salesloft_creds
);

Create External Tables for Salesloft

After creating the external data source, use CREATE EXTERNAL TABLE statements to link to Salesloft data from your SQL Server instance. The table column definitions must match those exposed by the CData ODBC Driver for Salesloft. 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 Salesloft Accounts would look similar to the following:

CREATE EXTERNAL TABLE Accounts(
  Id [nvarchar](255) NULL,
  Name [nvarchar](255) NULL,
  ...
) WITH ( 
  LOCATION='Accounts',
  DATA_SOURCE=cdata_salesloft_source
);

Having created external tables for Salesloft 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 Salesloft, freeing up local resources and computing power. Download a free, 30-day trial of the ODBC Driver for Salesloft and start working with live Salesloft data alongside your SQL Server data today.