![]() |
VOOZH | about |
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 Ariba Procurement, you get access to your SAP Ariba Procurement data directly alongside your SQL Server data. This article describes creating an external data source and external tables to grant access to live SAP Ariba Procurement data using T-SQL queries.
NOTE: PolyBase is only available on SQL Server 19 and above.
CData Connect AI provides a pure SQL Server interface for SAP Ariba Procurement, allowing you to query data from SAP Ariba Procurement without replicating the data to a natively supported database. Using optimized data processing out of the box, CData Connect AI pushes all supported SQL operations (filters, JOINs, etc.) directly to SAP Ariba Procurement, leveraging server-side processing to return the requested SAP Ariba Procurement data quickly.
Connectivity to SAP Ariba Procurement from PolyBase is made possible through CData Connect AI. To work with SAP Ariba Procurement data from PolyBase, we start by creating and configuring a SAP Ariba Procurement connection.
In order to connect with SAP Ariba Procurement, set the following:
After setting connection properties, you need to configure OAuth connectivity to authenticate.
For more information on creating an OAuth application, refer to the Help documentation.
After setting the following, you are ready to connect:
When you connect, the provider automatically completes the OAuth process:
When connecting to Connect AI through the REST API, the OData API, or the Virtual SQL Server, a Personal Access Token (PAT) is used to authenticate the connection to Connect AI. It is best practice to create a separate PAT for each service to maintain granularity of access.
With the connection configured and a PAT generated, you are ready to connect to SAP Ariba Procurement data from Polybase.
After configuring the connection, you need to create a credential database for the external data source.
Execute the following SQL command to create credentials for the external data source connected to SAP Ariba Procurement data.
NOTE: Set IDENTITY to your Connect AI username and set SECRET to your Personal Access Token.
CREATE DATABASE SCOPED CREDENTIAL ConnectCloudCredentials WITH IDENTITY = 'yourusername', SECRET = 'yourPAT';
Execute a CREATE EXTERNAL DATA SOURCE SQL command to create an external data source for SAP Ariba Procurement with PolyBase:
CREATE EXTERNAL DATA SOURCE ConnectCloudInstance WITH ( LOCATION = 'sqlserver://tds.cdata.com:14333', PUSHDOWN = ON, CREDENTIAL = ConnectCloudCredentials );
After creating the external data source, use CREATE EXTERNAL TABLE statements to link to SAP Ariba Procurement data from your SQL Server instance. The table column definitions must match those exposed by CData Connect AI. You can use the Data Explorer in Connect AI to see the table definition.
๐ Table definition in the Data Explorer (Salesforce is shown)Execute a CREATE EXTERNAL TABLE SQL command to create the external table(s), using the collation and setting the LOCATION to three-part notation for the connection, catalog, and table. The statement to create an external table based on a SAP Ariba Procurement Orders would look similar to the following.
CREATE EXTERNAL TABLE Orders( DocumentNumber COLLATE [nvarchar](255) NULL, Revision COLLATE [nvarchar](255) NULL, ... ) WITH ( LOCATION='SAPAribaProcurement1.SAPAribaProcurement.Orders', DATA_SOURCE=ConnectCloudInstance );
Having created external tables for SAP Ariba Procurement in your SQL Server instance, you are now able to query local and remote data simultaneously. To get live data access to hundreds of SaaS, Big Data, and NoSQL sources directly from your SQL Server database, try CData Connect AI today!
Learn more about CData Connect AI or sign up for free trial access:
Free Trial