How to connect PolyBase to Authorize.Net

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

Connect to Authorize.Net

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

You can obtain the necessary connection properties on the Security Settings -> General Settings page after logging into your Merchant Account.

• UseSandbox: The Authorize.Net API to be used to process transactions. If you are using a production account, this property can be left blank. If you are using a developer test account, set this to 'TRUE'.
• LoginID: The API login Id associated with your payment gateway account. This property is used to authenticate that you are authorized to submit website transactions. Note that this value is not the same as the login Id that you use to log in to the Merchant Interface.
• TransactionKey: The transaction key associated with your payment gateway account. This property is used to authenticate that you are authorized to submit website transactions.

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

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

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

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

Create an External Data Source for Authorize.Net

Execute a CREATE EXTERNAL DATA SOURCE SQL command to create an external data source for Authorize.Net with PolyBase:

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

For Authorize.Net, 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_authorizenet_source
WITH ( 
  LOCATION = 'odbc://SERVER_URL',
  CONNECTION_OPTIONS = 'DSN=CData Authorize.Net Sys',
  -- PUSHDOWN = ON | OFF,
  CREDENTIAL = authorizenet_creds
);

Create External Tables for Authorize.Net

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

CREATE EXTERNAL TABLE SettledBatchList(
  MarketType [nvarchar](255) NULL,
  TotalCharge [nvarchar](255) NULL,
  ...
) WITH ( 
  LOCATION='SettledBatchList',
  DATA_SOURCE=cdata_authorizenet_source
);

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