Ready to get started?

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

Download Now

Connect to Sugar CRM as an External Data Source using PolyBase

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

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

Connect to Sugar CRM

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

The User and Password properties, under the Authentication section, must be set to valid SugarCRM user credentials. This will use the default OAuth token created to allow client logins. OAuthClientId and OAuthClientSecret are required if you do not wish to use the default OAuth token.

You can generate a new OAuth consumer key and consumer secret in Admin -> OAuth Keys. Set the OAuthClientId to the OAuth consumer key. Set the OAuthClientSecret to the consumer secret.

Additionally, specify the URL to the SugarCRM account.

Note that retrieving SugarCRM metadata can be expensive. It is advised that you store the metadata locally as described in the "Caching Metadata" chapter of the help documentation.

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

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

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

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

Create an External Data Source for Sugar CRM

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

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

Create External Tables for Sugar CRM

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

CREATE EXTERNAL TABLE Accounts(
  Name [nvarchar](255) NULL,
  AnnualRevenue [nvarchar](255) NULL,
  ...
) WITH ( 
  LOCATION='Accounts',
  DATA_SOURCE=cdata_sugarcrm_source
);

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