---
schema_version: "1"
id: edad800c21291d3132d65c1a1394d6e6297f8fda1561a5c683be1178b4784bb9
title: Google BigQuery Standard SQL Connection
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/analytics/264-0-0/bi_integrate_connectors_googlebigquery_standard_sql.md
canonical_url: https://help.salesforce.com/s/articleView?id=analytics.bi_integrate_connectors_googlebigquery_standard_sql.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 8a9c87793c2a99aa08d97963edfff0afeb4e336824a6b5c0e73aa9d17e61331e
description: Bring your large volumes of Google BigQuery data with standard SQL support into CRM Analytics using the Google BigQuery Standard SQL connector.
products:
  - CRM Analytics
  - Cross Cloud
release: "264"
---
# Google BigQuery Standard SQL Connection

Bring your large volumes of Google BigQuery data with standard SQL support into CRM Analytics using the Google BigQuery Standard SQL connector.

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-analytics-bi-264-0-0-production-enus/ec791473-f5b4-4f64-a656-9104f455d966/images/icon_important.png)

Important Use the [Google BigQuery for Legacy SQL Connection](https://help.salesforce.com/articleView?id=bi_integrate_connectors_googlebigquery_settings.htm&language=en_US) instead of this connector if using legacy SQL.

## Create Connection

1. On the Data Manager Connections tab, click **New Connection**.
2. Click the name of the connector, and click **Next**.
3. Enter the connector settings.
4. To validate your settings and attempt to connect to the source, click **Save & Test**. If the connection fails, CRM Analytics shows possible reasons.

All settings require a value, unless otherwise indicated.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d166070e82">Connection Setting</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d166070e85">Description</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Connection Setting" class="slds-cell-wrap" style="vertical-align:top;" headers="d166070e82 ">Connection Name</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d166070e85 ">Identifies the connections. Use a convention that lets you easily distinguish
              between different connections.</td>

          </tr>
          <tr class="">
            <td data-label="Connection Setting" class="slds-cell-wrap" style="vertical-align:top;" headers="d166070e82 ">Developer Name</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d166070e85 ">API name for the connection. This name can’t include spaces. The API name is
              used in your recipes to reference data extracted through this connection. You can’t
              change the developer name after you create the connection.</td>

          </tr>
          <tr class="">
            <td data-label="Connection Setting" class="slds-cell-wrap" style="vertical-align:top;" headers="d166070e82 ">Description</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d166070e85 ">Description</td>

          </tr>
          <tr class="">
            <td data-label="Connection Setting" class="slds-cell-wrap" style="vertical-align:top;" headers="d166070e82 ">Schema</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d166070e85 ">Name of the Google BigQuery Dataset ID you’re connecting to.</td>

          </tr>
          <tr class="">
            <td data-label="Connection Setting" class="slds-cell-wrap" style="vertical-align:top;" headers="d166070e82 ">Private Key</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d166070e85 ">Enter the <code>private_key</code> value from the JSON
              file. </td>

          </tr>
          <tr class="">
            <td data-label="Connection Setting" class="slds-cell-wrap" style="vertical-align:top;" headers="d166070e82 ">Client Email</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d166070e85 ">
              <p>Enter the <code>client_email</code> value from the JSON
                file.</p>
              <p style="margin-bottom:0;">Don’t include <code>"private_key": "-----BEGIN
                    PRIVATE KEY-----"</code> at the start of the key, and <code>\n-----END PRIVATE KEY-----\n"</code> at the
                end.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Connection Setting" class="slds-cell-wrap" style="vertical-align:top;" headers="d166070e82 ">Project ID</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d166070e85 ">
              <p>Enter the <code>project_id</code> value from the JSON
                file.</p>
              <p style="margin-bottom:0;">If you have multiple projects with the same service account, enter the ID
                of the project containing the dataset that you want to connect to.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Connection Setting" class="slds-cell-wrap" style="vertical-align:top;" headers="d166070e82 ">Billing Project ID</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d166070e85 ">The ID for the Cloud Billing account you want this connection’s activity
              charged to.</td>

          </tr>
          <tr class="">
            <td data-label="Connection Setting" class="slds-cell-wrap" style="vertical-align:top;" headers="d166070e82 ">Use Storage API</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d166070e85 ">
              <p>Optional setting. </p>
              <p><samp class="parmname">True</samp>: Uses the Google BigQuery
                Storage Read API. See <a href="https://cloud.google.com/bigquery/docs/reference/storage" target="_blank">Google’s BigQuery Storage Read API</a> documentation to
                understand your expected consumption, and <a href="https://cloud.google.com/bigquery/pricing#storage-api" target="_blank">Google’s data extraction pricing</a> for additional cost
                information. </p>
              <p style="margin-bottom:0;"><samp class="parmname">False</samp>: Uses the Direct extract mode. This
                mode has a data limit of 10MB. </p>
            </td>

          </tr>
        </tbody>
      </table>

## Google BigQuery Standard SQL Connector Considerations

Keep these behaviors in mind when working with the Google BigQuery Standard SQL connector.

- Connected object names must start with a letter and contain only letters, digits, or underscores. Object names can’t end with an underscore.
- Only field names with combinations of alphanumeric, dot, underscore, or dash characters are supported. If a connector includes field names that contain other characters, such as spaces or brackets, the sync fails.
- The connector can sync up to 100 million rows or 50 GB per object, whichever limit is reached first.
- Staging mode is supported. Direct mode isn’t supported.
- BigQuery tables using data integrated from Google Drive aren’t supported. The Google Drive data must be moved into BigQuery.
- The connector doesn’t flatten nested fields. When previewing nested data before load, only the top-level fields are shown.

Temporary Destination Tables

The connector creates temporary destination tables in BigQuery to stage data before serving it to the client. The connector names these tables in the format EA\_TEMP\_<5-character random string>\_<objectName>. Tables are usually deleted automatically. To avoid incurring extra data storage costs on Google BigQuery, check that all temporary tables have been deleted, and manually delete any tables that haven’t been deleted.

Table Support

The Google BigQuery Standard SQL connector supports Standard SQL Tables, Legacy SQL Tables, and Standard SQL Views, but doesn’t support Legacy SQL Views.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-analytics-bi-264-0-0-production-enus/ec791473-f5b4-4f64-a656-9104f455d966/images/icon_note.png)

Note This connector uses the Google BigQuery Storage Read API for increased throughput, and may impact your Google billing. You may see a nominal cost increase per TB if you're not on a flat-rate plan. See [Google’s BigQuery Storage Read API](https://cloud.google.com/bigquery/docs/reference/storage) documentation to understand your expected consumption, and [Google’s data extraction pricing](https://cloud.google.com/bigquery/pricing#storage-api) for additional cost information.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small " summary="Additional Settings Required for Legacy Connector">
        <caption>Additional Settings Required for Legacy Connector</caption>
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d166070e299">Setting</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d166070e302">Description</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Setting" class="slds-cell-wrap" style="vertical-align:top;" headers="d166070e299 ">Storage Path</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d166070e302 ">
              <p>Applicable only to the legacy connector version. Path in Google Cloud Storage
                where a local stage file is created to store the data temporarily. Enter the bucket
                name or the bucket name and folder name. For example, enter
                <kbd>&lt;bucket_name&gt;</kbd> or
                <kbd>&lt;bucket_name&gt;/&lt;folder_name&gt;</kbd>.
              </p>
              <p style="margin-bottom:0;">To write files to this
                staging area, the user specified in Client Email must have the list, read, and
                write permissions on the bucket.</p>
            </td>

          </tr>
        </tbody>
      </table>