Ready to get started?

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

Download Now

Connect to Wasabi as an External Data Source using PolyBase

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

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

Connect to Wasabi

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

To authorize Wasabi requests, provide the credentials for an administrator account or for an IAM user with custom permissions. Set AccessKey to the access key Id. Set SecretKey to the secret access key.

Note: You can connect as the AWS account administrator, but it is recommended to use IAM user credentials to access AWS services.

For information on obtaining the credentials and other authentication methods, refer to the Getting Started section of the Help documentation.

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

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

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

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

Create an External Data Source for Wasabi

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

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

Create External Tables for Wasabi

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

CREATE EXTERNAL TABLE Buckets(
  Name [nvarchar](255) NULL,
  OwnerId [nvarchar](255) NULL,
  ...
) WITH ( 
  LOCATION='Buckets',
  DATA_SOURCE=cdata_wasabi_source
);

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