Connect to Oracle Sales as an External Data Source using PolyBase

Ready to get started?

Download for a free trial:

Download Now

Learn more:

Oracle Sales ODBC Driver

The Oracle Sales ODBC Driver is a powerful tool that allows you to connect with live Oracle Sales data, directly from any applications that support ODBC connectivity.

Access Oracle Sales like you would a database - read, write, and update Leads, Contacts, Opportunities, Accounts, etc. through a standard ODBC Driver interface.



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

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

Connect to Oracle Sales

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

Oracle Sales uses Basic authentication over SSL; after setting the following connection properties, you are ready to connect:

  • Username: Set this to the user name that you use to log into your Oracle Cloud service.
  • Password: Set this to your password.
  • HostURL: Set this to the Web address (URL) of your Oracle Cloud service.

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

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

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

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

Create an External Data Source for Oracle Sales

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

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

Create External Tables for Oracle Sales

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

CREATE EXTERNAL TABLE Opportunities(
  OptyId [nvarchar](255) NULL,
  Name [nvarchar](255) NULL,
  ...
) WITH ( 
  LOCATION='Opportunities',
  DATA_SOURCE=cdata_oraclesalescloud_source
);

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