Ready to get started?

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

Download Now

Connect to DigitalOcean as an External Data Source using PolyBase

Use the CData ODBC Driver for DigitalOcean and PolyBase to create an external data source in SQL Server 2019 with access to live DigitalOcean 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 DigitalOcean, you get access to your DigitalOcean data directly alongside your SQL Server data. This article walks through creating an external data source and external tables to grant access to live DigitalOcean data using T-SQL queries.

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

Connect to DigitalOcean

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

DigitalOcean uses OAuth 2.0 authentication. To authenticate using OAuth, you can use the embedded credentials or register an app with DigitalOcean.

See the Getting Started guide in the CData driver documentation for more information.

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

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

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

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

Create an External Data Source for DigitalOcean

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

For DigitalOcean, 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_digitalocean_source
WITH ( 
  LOCATION = 'odbc://SERVERNAME[:PORT]',
  CONNECTION_OPTIONS = 'DSN=CData DigitalOcean Sys',
  -- PUSHDOWN = ON | OFF,
  CREDENTIAL = digitalocean_creds
);

Create External Tables for DigitalOcean

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

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

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