Ready to get started?

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

Download Now

Connect to Sage 300 as an External Data Source using PolyBase

Use the CData ODBC Driver for Sage 300 and PolyBase to create an external data source in SQL Server 2019 with access to live Sage 300 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 300, you get access to your Sage 300 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 300 data using T-SQL queries.

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

Connect to Sage 300

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

Sage 300 requires some initial setup in order to communicate over the Sage 300 Web API.

  • Set up the security groups for the Sage 300 user. Give the Sage 300 user access to the option under Security Groups (per each module required).
  • Edit both web.config files in the /Online/Web and /Online/WebApi folders; change the key AllowWebApiAccessForAdmin to true. Restart the webAPI app-pool for the settings to take.
  • Once the user access is configured, click https://server/Sage300WebApi/ to ensure access to the web API.

Authenticate to Sage 300 using Basic authentication.

Connect Using Basic Authentication

You must provide values for the following properties to successfully authenticate to Sage 300. Note that the provider reuses the session opened by Sage 300 using cookies. This means that your credentials are used only on the first request to open the session. After that, cookies returned from Sage 300 are used for authentication.

  • Url: Set this to the url of the server hosting Sage 300. Construct a URL for the Sage 300 Web API as follows: {protocol}://{host-application-path}/v{version}/{tenant}/ For example, http://localhost/Sage300WebApi/v1.0/-/.
  • User: Set this to the username of your account.
  • Password: Set this to the password of your account.

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

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

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

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

Create an External Data Source for Sage 300

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

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

Create External Tables for Sage 300

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

CREATE EXTERNAL TABLE OEInvoices(
  InvoiceUniquifier [nvarchar](255) NULL,
  ApprovedLimit [nvarchar](255) NULL,
  ...
) WITH ( 
  LOCATION='OEInvoices',
  DATA_SOURCE=cdata_sage300_source
);

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