Ready to get started?

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

Download Now

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

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

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

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

Google Drive への接続

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

You can connect to Google APIs on behalf of individual users or on behalf of a domain. Google uses the OAuth authentication standard. See the "Getting Started" section of the help documentation for a guide.

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

Google Drive 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 Drive data.

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

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

Create an External Data Source for Google Drive

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

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

Google Drive のExternal Table を作成

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

CREATE EXTERNAL TABLE Files(
  Name [nvarchar](255) NULL,
  Size [nvarchar](255) NULL,
  ...
) WITH ( 
  LOCATION='Files',
  DATA_SOURCE=cdata_googledrive_source
);

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

 
 
ダウンロード