Ready to get started?

Learn more about the CData ODBC Driver for DocuSign or download a free trial:

Download Now

Connect to DocuSign as an External Data Source using PolyBase

Use the CData ODBC Driver for DocuSign and PolyBase to create an external data source in SQL Server 2019 with access to live DocuSign data.

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

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

Connect to DocuSign

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

To connect to DocuSign, set the following connection properties:

  • UseSandbox: indicates whether current user account is sandbox or not (FALSE by default)
  • AccountId (optional): set it in the connection string if you have access to multiple Account Ids

Authenticating to DocuSign

DocuSign uses the OAuth authentication standard. To authenticate using OAuth, you will need to create an app to obtain the OAuthClientId, OAuthClientSecret, and CallbackURL connection properties. See the Help documentation more information.

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

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

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

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

Create an External Data Source for DocuSign

Execute the following SQL command to create an external data source for DocuSign with PolyBase, using the DSN and credentials configured earlier.

For DocuSign, set SERVERNAME to 'localhost' or '127.0.0.1' and 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_docusign_source
WITH ( 
  LOCATION = 'odbc://SERVERNAME[:PORT]',
  CONNECTION_OPTIONS = 'DSN=CData DocuSign Sys',
  -- PUSHDOWN = ON | OFF,
  CREDENTIAL = docusign_creds
);

Create External Tables for DocuSign

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

CREATE EXTERNAL TABLE Documents(
  DocumentId [nvarchar](255) NULL,
  DocumentName [nvarchar](255) NULL,
  ...
) WITH ( 
  LOCATION='Documents',
  DATA_SOURCE=cdata_docusign_source
);

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