Ready to get started?

Download a free trial of the Google BigQuery ODBC Driver to get started:

 Download Now

Learn more:

Google BigQuery Icon Google BigQuery ODBC Driver

The Google BigQuery ODBC Driver is a powerful tool that allows you to connect with live Google BigQuery data, directly from any applications that support ODBC connectivity.

Access Google BigQuery like you would a database - read, write, and update Datasets, Tables, etc. through a standard ODBC Driver interface.

How to create BigQuery federated tables in MySQL



Use the SQL Gateway and the ODBC Driver to set up federated tables for BigQuery data in MySQL .

You can use the SQL Gateway to configure a MySQL remoting service and set up federated tables for BigQuery data. The service is a daemon process that provides a MySQL interface to the CData ODBC Driver for BigQuery: After you have started the service, you can create a server and tables using the FEDERATED Storage Engine in MySQL. You can then work with BigQuery data just as you would local MySQL tables.

Connect to BigQuery Data

If you have not already done so, provide values for the required connection properties in the data source name (DSN). You can use the built-in Microsoft ODBC Data Source Administrator to configure the DSN. This is also the last step of the driver installation. See the "Getting Started" chapter in the help documentation for a guide to using the Microsoft ODBC Data Source Administrator to create and configure a DSN.

Google uses the OAuth authentication standard. To access Google APIs on behalf of 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, you will need to specify the DatasetId and ProjectId. See the "Getting Started" chapter of the help documentation for a guide to using OAuth.

Configure the SQL Gateway

See the SQL Gateway Overview to set up connectivity to BigQuery data as a virtual MySQL database. You will configure a MySQL remoting service that listens for MySQL requests from clients. The service can be configured in the SQL Gateway UI.

Creating a MySQL Remoting Service in SQL Gateway (Salesforce is shown)

Create a FEDERATED Server and Tables for BigQuery Data

After you have configured and started the service, create a FEDERATED server to simplify the process of creating FEDERATED tables:

Create a FEDERATED Server

The following statement will create a FEDERATED server based on the ODBC Driver for BigQuery. Note that the username and password of the FEDERATED server must match a user account you defined on the Users tab of the SQL Gateway.

CREATE SERVER fedGoogleBigQuery
FOREIGN DATA WRAPPER mysql
OPTIONS (USER 'sql_gateway_user', PASSWORD 'sql_gateway_passwd', HOST 'sql_gateway_host', PORT ####, DATABASE 'CData GoogleBigQuery Sys');

Create a FEDERATED Table

To create a FEDERATED table using our newly created server, use the CONNECTION keyword and pass the name of the FEDERATED server and the remote table (Orders). Refer to the following template for the statement to create a FEDERATED table:

CREATE TABLE fed_orders (
  ...,
  ordername  TYPE(LEN),
  freight  TYPE(LEN),
  ...,
)
ENGINE=FEDERATED
DEFAULT CHARSET=latin1
CONNECTION='fedGoogleBigQuery/orders';

NOTE: The table schema for the FEDERATED table must match the remote table schema exactly. You can always connect directly to the MySQL remoting service using any MySQL client and run a SHOW CREATE TABLE query to get the table schema.

Execute Queries

You can now execute queries to the BigQuery FEDERATED tables from any tool that can connect to MySQL, which is particularly useful if you need to JOIN data from a local table with data from BigQuery. Refer to the following example:

SELECT 
  fed_orders.ordername, 
  local_table.custom_field 
FROM 
  local_table 
JOIN 
  fed_orders 
ON 
  local_table.foreign_ordername = fed_orders.ordername;