How to connect PolyBase to Google Campaign Manager 360

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 Google Campaign Manager 360, you get access to your Google Campaign Manager 360 data directly alongside your SQL Server data. This article describes creating an external data source and external tables to grant access to live Google Campaign Manager 360 data using T-SQL queries.

NOTE: PolyBase is only available on SQL Server 19 and above, and only for Standard SQL Server.

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

Connect to Google Campaign Manager 360

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 Google Campaign Manager 360 Sys is created automatically).

Google Campaign Manager uses the OAuth authentication standard. The data provider facilitates OAuth in various ways as described below. The following OAuth flow requires the authenticating user to interact with DoubleClick Campaign Manager, using the browser. You can also use a service account to authenticate.

For authentication guides, see the Getting Started section of the data provider help documentation.

Click "Test Connection" to ensure that the DSN is connected to Google Campaign Manager 360 properly. Navigate to the Tables tab to review the table definitions for Google Campaign Manager 360.

Create an External Data Source for Google Campaign Manager 360 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 Google Campaign Manager 360 data.

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

Create an External Data Source for Google Campaign Manager 360

Execute a CREATE EXTERNAL DATA SOURCE SQL command to create an external data source for Google Campaign Manager 360 with PolyBase:

• Set the LOCATION parameter , using the DSN and credentials configured earlier.

For Google Campaign Manager 360, set SERVERNAME to the URL or address for your server (e.g. 'localhost' or '127.0.0.1' for local servers; the remote URL for remote servers). 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_googlecm_source
WITH ( 
  LOCATION = 'odbc://SERVER_URL',
  CONNECTION_OPTIONS = 'DSN=CData Google Campaign Manager 360 Sys',
  -- PUSHDOWN = ON | OFF,
  CREDENTIAL = googlecm_creds
);

Create External Tables for Google Campaign Manager 360

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

CREATE EXTERNAL TABLE CampaignPerformance(
  Clicks [nvarchar](255) NULL,
  Device [nvarchar](255) NULL,
  ...
) WITH ( 
  LOCATION='CampaignPerformance',
  DATA_SOURCE=cdata_googlecm_source
);

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