Ready to get started?

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

Download Now

Connect to Google Ads as an External Data Source using PolyBase

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

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

Connect to Google Ads

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

Google uses the OAuth authentication standard. To access Google APIs on behalf on individual users, you can use the embedded credentials or you can register your own OAuth app.

OAuth also enables you to use a service account to connect on behalf of users in a Google Apps domain. To authenticate with a service account, you will need to register an application to obtain the OAuth JWT values.

In addition to the OAuth values, specify the DeveloperToken and ClientCustomerId.

See the "Getting Started" chapter of the help documentation for a guide to using OAuth.

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

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

NOTE: Since Google Ads does not require a User or Password to authenticate, you may use whatever values you wish for IDENTITY and SECRET.

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

Create an External Data Source for Google Ads

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

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

Create External Tables for Google Ads

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

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

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