Ready to get started?

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

Download Now

PolyBase で外部データソースとしてGoogle Campaign Manager を連携利用

CData ODBC Driver for Google Campaign Manager とSQL Server 2019 のPolyBase を使って、リアルタイムGoogle Campaign Manager data に外部データソースとしてアクセス。

SQL Server のPolyBase は、データベーステーブルをクエリするTransact-SQL シンタックスを使って、外部データにクエリする仕組みです。 CData ODBC Drivers for Google Campaign Manager data を組み合わせて使うことで、SQL Server データと同じようにGoogle Campaign Manager data へのアクセスが可能です。 本記事では、PolyBase 外部データソースへのGoogle Campaign Manager data の設定から、T-SQL クエリを使ったGoogle Campaign Manager data へのアクセスを行います。

The CData ODBC drivers offer unmatched performance for interacting with live Google Campaign Manager 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, the driver pushes down supported SQL operations, like filters and aggregations, directly to Google Campaign Manager 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 data, using a single query to pull data from distributed sources.

Google Campaign Manager への接続

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 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 properly. Navigate to the Tables tab to review the table definitions for Google Campaign Manager.

Google Campaign Manager 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.


Creating a Credential Database

Execute the following SQL command to create credentials for the external data source connected to Google Campaign Manager data.

WITH IDENTITY = 'username', SECRET = 'password';

Create an External Data Source for Google Campaign Manager

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

For Google Campaign Manager, set SERVERNAME to 'localhost' or '' 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_googlecm_source
  CONNECTION_OPTIONS = 'DSN=CData Google Campaign Manager Sys',
  CREDENTIAL = googlecm_creds

Google Campaign Manager のExternal Table を作成

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

CREATE EXTERNAL TABLE CampaignPerformance(
  Clicks [nvarchar](255) NULL,
  Device [nvarchar](255) NULL,
) WITH ( 

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