How to connect PolyBase to Oracle SCM

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 Oracle SCM, you get access to your Oracle SCM data directly alongside your SQL Server data. This article describes creating an external data source and external tables to grant access to live Oracle SCM 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 Oracle SCM data using PolyBase due to optimized data processing built into the driver. When you issue complex SQL queries from SQL Server to Oracle SCM, the driver pushes down supported SQL operations, like filters and aggregations, directly to Oracle SCM 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 Oracle SCM data, using a single query to pull data from distributed sources.

Connect to Oracle SCM

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

The following connection properties are required to connect to Oracle SCM data.

• Url: The URL of the account that you want to connect to. Typically, this will be the URL of your Oracle Cloud service. For example, https://servername.fa.us2.oraclecloud.com.
• User: The username of your Oracle Cloud service account.
• Password: The password of your Oracle Cloud service account.

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

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

NOTE: IDENTITY and SECRET correspond with the User and Password properties for Oracle SCM.

CREATE DATABASE SCOPED CREDENTIAL oraclescm_creds
WITH IDENTITY = 'oraclescm_username', SECRET = 'oraclescm_password';

Create an External Data Source for Oracle SCM

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

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

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

Create External Tables for Oracle SCM

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

CREATE EXTERNAL TABLE Carriers(
  CarrierId [nvarchar](255) NULL,
  CarrierName [nvarchar](255) NULL,
  ...
) WITH ( 
  LOCATION='Carriers',
  DATA_SOURCE=cdata_oraclescm_source
);

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