Ready to get started?

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

Download Now

Connect to OFX as an External Data Source using PolyBase

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

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

Connect to OFX

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

The OFXUser and OFXPassword properties, under the Authentication section, must be set to valid OFX user credentials. In addition to this, you will need to configure FIURL, FIOrganizationName, and FIID, which will be specific for the financial institution. You will also need to provide application-specific settings, including OFXVersion, ApplicationVersion, and ApplicationId.

To connect to some services, you will need to provide additional account information such as AccountId, AccountType, BankId, BrokerId, and CCNumber.

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

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

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

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

Create an External Data Source for OFX

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

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

Create External Tables for OFX

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

CREATE EXTERNAL TABLE InvBalances(
  Id [nvarchar](255) NULL,
  Amount [nvarchar](255) NULL,
  ...
) WITH ( 
  LOCATION='InvBalances',
  DATA_SOURCE=cdata_ofx_source
);

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