Looking for the previous version? View v2024.06 documentation →
Google BigQuery Profile — JDBC Connection
Create a Google BigQuery connection profile in Data Trust using the Simba JDBC driver and an OAuth-based connection string.
Overview
Data Trust supports connecting to Google BigQuery via a JDBC connection string using the Simba BigQuery JDBC driver. This connection type allows you to run reconciliation scenarios, validation queries, and data quality jobs directly against BigQuery datasets.
ProjectId, OAuthType, and service-account or OAuth credentials) before creating this profile.Prerequisites
- You are logged in to Data Trust with an Admin Pro-User role.
- You have a valid Google BigQuery JDBC connection string, the Simba BigQuery JDBC driver class (
com.simba.googlebigquery.jdbc42.Driver), and the required OAuth or service-account credentials.
Creating a Google BigQuery JDBC Connection
Path: Data Trust › Admin Console › Connection Explorer › + New Connection- Navigate to Admin Console › Connection Explorer and click + New Connection.
Figure 1: Connection Explorer — click “+ New Connection” to begin creating a Google BigQuery profile.
The Connection Explorer shows all existing profiles. Click + New Connection at the top-right to open the Create Connection form.
Figure 2: Create Connection page — enter a Connection Name and select “Google Big Query” as the Source Name.
On the Create Connection page, enter a unique Connection Name (e.g., GoogleBig Query). Then open the Source Name dropdown and select Google Big Query. The right panel will update to show the BigQuery-specific connection parameter fields.
- Enter a unique Connection Name.
- Select Google Big Query from the Source Name dropdown.
- Fill in the Connection Parameters tab:
Figure 3: Google BigQuery connection parameters — Connection String, User Name, Password, Driver Class, and TENANT fields.
The Google BigQuery connection form shows: Connection String (the full Simba JDBC URL, e.g., jdbc:bigquery://https://www.googleapis.com/bigquery/v2:443;ProjectId=your-project;OAuthType=0;OAuthServiceAcctEmail=...;OAuthPvtKeyPath=...), User Name (optional for OAuth flows), Password, Driver Class (must be com.simba.googlebigquery.jdbc42.Driver), and TENANT (optional).
| Field | Value |
|---|---|
| Connection String | Full Simba BigQuery JDBC URL including ProjectId, OAuthType, and authentication parameters. |
| User Name | Leave blank if using service-account OAuth authentication. |
| Password | Leave blank if using service-account OAuth authentication. |
| Driver Class | com.simba.googlebigquery.jdbc42.Driver |
| TENANT | Optional — Google Cloud organisation tenant ID if required. |
- Click the Additional Settings tab and configure parallelism, packet sizes, and user group access as needed.
Figure 4: Additional Settings tab — configure parallelism and packet sizes for the BigQuery connection.
The Additional Settings tab for BigQuery follows the same structure as other JDBC connections. Set appropriate parallelism values based on your BigQuery quota and expected concurrency. Assign the relevant User Groups so the right teams can use this connection.
Figure 5: Additional Settings — all configurable fields including User Groups and the optional Query Timeout.
Scroll down in the Additional Settings tab to see all available options. The User Groups multi-select determines which teams have access to this BigQuery profile. Query Timeout In Seconds is optional but recommended for BigQuery to avoid unexpected cost from long-running queries.
- Click Test Connection to validate the BigQuery credentials and network connectivity.
Figure 6: Click “Test Connection” to verify the BigQuery JDBC connection string and credentials.
The Test Connection button sends a connection attempt to BigQuery using the supplied JDBC string. This validates that the Project ID, OAuth type, authentication credentials, and driver class are all correct. Ensure the Data Trust server has outbound network access to googleapis.com on port 443.
A green “Test Connection Successful!” toast confirms the connection is valid.
Figure 7: Green “Test Connection Successful!” toast — the BigQuery JDBC connection is verified and ready to save.
The green toast confirms Data Trust can authenticate against your BigQuery project. If the test fails, check the connection string parameters (especially OAuthType, OAuthServiceAcctEmail, and OAuthPvtKeyPath) and ensure the service account has BigQuery Data Viewer and Job User roles.
- Click Save to create the connection profile.
The Google BigQuery profile appears in the Connection Explorer and is immediately available for use in scenarios and queries.
Figure 8: Connection Explorer — the Google BigQuery connection profile is now listed and available for use across Data Trust.
The new Google BigQuery profile appears in the Connection Explorer table with its Source Name shown as Databricks or Google Big Query. It is now available in the connection dropdown in Query Studio, Scenario Builder, and any other Data Trust module that requires a database connection.