Ready to get started?

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

Download Now

Connect to Sage 200 as an External Data Source using PolyBase

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

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

Connect to Sage 200

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

  • Schema: Determines which Sage 200 edition you are connecting to. Specify either StandardUK or ProfessionalUK.
  • Subscription Key: Provides access to the APIs that are used to establish a connection. You will first need to log into the Sage 200 API website and subscribe to the API edition that matches your account. You can do so here: https://developer.columbus.sage.com/docs/services/api/uk. Afterwards, the subscription key may be found in your profile after logging into Sage 200.

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

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

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

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

Create an External Data Source for Sage 200

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

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

Create External Tables for Sage 200

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

CREATE EXTERNAL TABLE Banks(
  Id [nvarchar](255) NULL,
  Code [nvarchar](255) NULL,
  ...
) WITH ( 
  LOCATION='Banks',
  DATA_SOURCE=cdata_sage200_source
);

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