TIBCO Scribe® Online Connector For Google BigQuery

The TIBCO Scribe® Online Connector for Google BigQuery allows you to easily integrate your Google BigQuery databases with other business systems such as ERP, CRM, and Marketing Automation. This Connector discovers tables, views, and columns. In addition, you can use native SQL queries to access, filter, and join your data.

Use the Google BigQuery Connector as a source or target Connection for Integration Solutions. This Connector is based on the Scribe.Connector.AdoNet library and CData Google BigQuery ADO.NET provider.

Use the TIBCO Scribe® Connector for Google BigQuery to:

Connector Specifications


Agent Types

On Premise X
Cloud X

Replication Services


Integration Services

Source X
Target X

Migration Services



Integration X
Request-Reply X

This Connector is available from the TIBCO Scribe® Online Marketplace. See Marketplace TIBCO Scribe® Certified Connectors for more information.

Supported Entities

Setup Considerations

Advanced considerations, such as customizing the SSL configuration, or connecting through a firewall or a proxy, are described in the Advanced Settings section of the CData documentation.

API Usage Limits

Google BigQuery limits the number of API calls per project per day and the number of queries per second per IP address. Refer to Quotas and limits in the Google BigQuery documentation for exact limits.

Note: Refreshing metadata for the Connector consumes API calls.

Selecting An Agent Type For Google BigQuery

Refer to TIBCO Scribe® Online Agents for information on available Agent types and how to select the best Agent for your Solution.

Connecting To Google BigQuery

Note: Best practice is to create Connections with credentials that limit permissions in the target system, following the principle of least privilege. Using Administrator level credentials in a Connection provides Administrator level access to the target system for TIBCO Scribe® Online users. Depending on the entities supported, a TIBCO Scribe® Online user could alter user accounts in the target system.

  1. Select More > Connections from the menu.
  2. From the Connections page select Add to open the Add a New Connection dialog.
  3. Select the Connector from the drop-down list in the Connection Type field, and then enter the following information for this Connection:
    • Name — This can be any meaningful name, up to 25 characters.
    • Alias — An alias for this Connection name. The alias is generated from the Connection name, and can be up to 25 characters. The Connection alias can include letters, numbers, and underscores. Spaces and special characters are not accepted. You can change the alias. For more information, see Connection Alias.
    • ProjectId — Id of the project where you want to connect. ProjectId of the billing project for executing jobs. Obtain the project Id in the Google API console: In the main menu, select API Project and copy the Id.
    • DataSetId — Dataset where you want to connect and view tables.
    • OAuth Verifier Code — Unique authorization code returned by Google for your account when you click the Get Verifier Code button. After saving the Connection, this code no longer displays but is stored in the database for use when connecting to Google BigQuery.
    • Additional Parameters — Optional field where you can specify one or more connection string parameters. See the Connection String Options section of the CData documentation for a list of parameters that can be used and their default values. Note that in some cases the CData PostgreSQL ADO.NET provider does not fully support all of the possible parameters.

      Syntax for the Additional Parameters field is as follows:

      • Schema name is required for tables and views in the format schemaname.tablename or schemaname.viewname. For example: Tables=scribe.mhs_test;Views=scribe.mhs_list;Timeout=300;
      • All blank characters, except those within a value or within quotation marks, are ignored
      • Preceding and trailing spaces are ignored unless enclosed in single or double quotes, such as Keyword=" value"
      • Semicolons (;) within a value must be delimited by quotation marks
      • Use a single quote (') if the value begins with a double quote (")
      • Use a double quote (") if the value begins with a single quote (')
      • Parameters are case-insensitive
      • If a KEYWORD=VALUE pair occurs more than once in the connection string, the value associated with the last occurrence is used
      • If a keyword contains an equal sign (=), it must be preceded by an additional equal sign to indicate that the equal sign is part of the keyword
      • Parameters that are handled by other fields or default settings in the Connection dialog are ignored if used in the Additional Parameters field, including: 
        • Logfile — To enable logging enter a value for the verbosity parameter in the Additional Parameters field. The default log file size is a maximum of 10MB. When the log file reaches 10MB a new log file is started, up to a maximum of five files. Once there are five files, the oldest file is deleted as needed. Any CData log files generated by this setting are stored in the default TIBCO Scribe® Online Agent Logs directory, C:\Program Files (x86)\Scribe Software\TIBCO Scribe® Online Agent\logs\.

          Note: For information on setting log file verbosity, see Verbosity in the CData Help.

        • MaxLogFileCount — This parameter is set by the Connector to a maximum of five files.
        • MaxLogFileSize — This parameter is set by the Connector to a maximum of 10MB.
        • Other
        • RTK
        • UseConnectionPooling
  4. Click the Get Verifier Code button and in the new browser tab log into your Google Platform account. If this is the first time you are accessing your account from the Connection dialog, an account confirmation message displays. Click Continue.

  5. When the Verifier Code displays, copy it and paste the code into the OAuth Verifier Code field on the Connection dialog.

    Note: The Verifier Code expires quickly. If you test your Connection and it fails, it may be because the code has expired. Click the Get Verifier Code button again and quickly copy and paste the new code.

    After you configure and save this Connection, the Verifier Code no longer displays on the Connection dialog, but it is stored in the database for use when connecting to Google BigQuery.

  6. Select Test to ensure that the Agent can connect to your database. Be sure to test the Connection against all Agents that use this Connection. See Testing Connections.
  7. Select OK to save the Connection.

Metadata Notes

Consider the following for Google BigQuery data fields and entity types.

Object definitions are dynamically generated based on the table definitions within Google BigQuery for the Project and Dataset specified in the connection.

The Execute Block displays on the Map designer, however, using Stored Procedures to generate metadata is not supported.


Connection metadata must have unique entity, relationship, and field names. If your Connection metadata has duplicate names, review the source system to determine if the duplicates can be renamed.

Retry Logic

If a request fails, the Connector does not retry.

Google BigQuery Connector As IS Source

Consider the following when using the Google BigQuery Connector as an IS source.

Native Query

The Google BigQuery Connector supports SQL queries in Native Query Blocks to create customized queries for Google BigQuery. The query can be as simple or complex as you need it to be; however, it should return a single result set. The native query text is sent to Google BigQuery exactly as it is entered without any modifications.

You can use SELECT , UPDATE , INSERT and DELETE clauses. If support for Enhanced SQL is enabled, you can use Joins, Aggregate functions, Projection Functions, and Predicate Functions. For additional details, see the SQL Compliance section of the CData documentation .

After entering the SQL query, you must select Test to validate the query. Invalid queries are not accepted by the Connector. See Native Query Block and Creating Native Queries For Microsoft SQL Server for additional information.

When testing a Native Query in a Map, if the source datastore does not return any data, TIBCO Scribe® Online cannot build the schema for the underlying metadata and the Map cannot be saved. To allow TIBCO Scribe® Online to build the schema, do the following:

  1. Create a single temporary record in the source datastore that matches the Native Query.
  2. Test the Native Query and ensure that it is successful.
  3. Save the Map.
  4. Remove the temporary record from the source datastore.

Net Change

When a datetime is configured on the Query Block on the Block Properties Net Change Tab to query for new and updated records, that configuration is treated as an additional filter. The Net Change datetime filter is applied as an AND after any other filters specified on the Block Properties Filter Tab. TIBCO Scribe® Online builds a query combining both the Net Change filter and the filters on the Filter tab. See Net Change And Filters for an example.

Some Connectors for TIBCO Scribe® Online only support one filter. For those Connectors you can use either Net Change or one filter on the Filter tab, not both.

Note: The Net Change date is ignored when previewing data on the Preview tab. Filters on the Block Properties Filters tab are used to filter the data on the Preview tab.


Filtering support varies by entity. For additional details, see the Data Model section of the CData documentation.

Google BigQuery Connector As IS Target

Consider the following when using the Google BigQuery Connector as an IS target.

Notes On Standard Entities

Special information about standard entities appears below.

TIBCO Scribe® Online API Considerations

Note: Connectors using OAuth for authentication are not fully supported by the TIBCO Scribe® Online API at this time.

License Agreement

The TIBCO Scribe® Online End User License Agreement for the Google BigQuery Connector describes TIBCO and your legal obligations and requirements. TIBCO suggests that you read the End User License Agreement.

More Information

For additional information on this Connector, refer to the Knowledge Base and Discussions in the TIBCO Community.