Ready to get started?

Learn more about the CData ODBC Driver for SAP Business One DI or download a free trial:

Download Now

Connect to SAP Business One DI as an External Data Source using PolyBase

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

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

Connect to SAP Business One DI

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 SAP Business One DI Sys is created automatically).

To connect to SAP Business One DI data, specify the following connection properties:

  • DBServerType: The type of server being connected to.
  • Server: The name or IP address of the Business One DI server to connect to.
  • CompanyDB: The company to connect to.
  • User: The username used when connecting to the LicenseServer.
  • Password: The password used when connecting to the LicenseServer.
  • LicenseServer (optional): Set this if your License Server is different from the Server.
  • UseTrusted (optional): Set to TRUE to connect using Windows credentials.

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

Create an External Data Source for SAP Business One DI 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 SAP Business One DI data.

NOTE: IDENTITY and SECRET correspond with the User and Password properties for SAP Business One DI.

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

Create an External Data Source for SAP Business One DI

Execute the following SQL command to create an external data source for SAP Business One DI 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_sapbusinessonedi_source
WITH ( 
  LOCATION = 'odbc://SERVERNAME[:PORT]',
  CONNECTION_OPTIONS = 'DSN=CData SAP Business One DI Sys',
  -- PUSHDOWN = ON | OFF,
  CREDENTIAL = sapbusinessonedi_creds
);

Create External Tables for SAP Business One DI

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

CREATE EXTERNAL TABLE OACT(
  AcctCode [nvarchar](255) NULL,
  AcctName [nvarchar](255) NULL,
  ...
) WITH ( 
  LOCATION='OACT',
  DATA_SOURCE=cdata_sapbusinessonedi_source
);

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