Ready to get started?

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

Download Now

Connect to FedEx as an External Data Source using PolyBase

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

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

Connect to FedEx

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

There are five pieces of information needed in order to authenticate its actions with the FedEx service. This information is below.

  • Server: This controls the URL where the requests should be sent. Common testing options for this are: "https://gatewaybeta.fedex.com:443/xml", "https://wsbeta.fedex.com:443/xml", "https://gatewaybeta.fedex.com:443/web-service", and "https://wsbeta.fedex.com:443/web-service"
  • DeveloperKey: This is the identifier part of the authentication key for the sender's identity. This value will be provided to you by FedEx after registration.
  • Password: This is the secret part of the authentication key for the sender's identity. This value will be provided to you by FedEx after registration.
  • AccountNumber: This valid 9-digit FedEx account number is used for logging into the FedEx server.
  • MeterNumber: This value is used for submitting requests to FedEx. This value will be provided to you by FedEx after registration.
  • PrintLabelLocation: This property is required if one intends to use the GenerateLabels or GenerateReturnLabels stored procedures. This should be set to the folder location where generated labels should be stored.

The Cache Database

Many of the useful tasks available from FedEx require a lot of data. To ensure this data is easy to input and recall later, utilizes a cache database to make these requests. You must set the cache connection properties:

  • CacheProvider: The specific database you are using to cache with. For example, org.sqlite.JDBC.
  • CacheConnection: The connection string to be passed to the cache provider. For example, jdbc:sqlite:C:\users\username\documents\fedexcache.db

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

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

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

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

Create an External Data Source for FedEx

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

PUSHDOWN is set to ON by default, meaning the ODBC Driver can leverage server-side processing for complex queries.

CREATE EXTERNAL DATA SOURCE cdata_fedex_source
WITH ( 
  LOCATION = 'odbc://SERVERNAME[:PORT]',
  CONNECTION_OPTIONS = 'DSN=CData FedEx Sys',
  -- PUSHDOWN = ON | OFF,
  CREDENTIAL = fedex_creds
);

Create External Tables for FedEx

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

CREATE EXTERNAL TABLE Senders(
  FirstName [nvarchar](255) NULL,
  Phone [nvarchar](255) NULL,
  ...
) WITH ( 
  LOCATION='Senders',
  DATA_SOURCE=cdata_fedex_source
);

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