Connection to BigQuery
To connect Google BigQuery to the DQC Platform, you’ll need to provide a service account with read-only access and supply a few key connection values. This article walks you through the setup.
Add a BigQuery connector
To get started:
Navigate to the Data Connectors screen in the DQC Platform
Click on BigQuery
Fill in the required connection fields as described below
Start the setup by selecting BigQuery from the connector list
Required connection information
Field | Example | Description |
|---|---|---|
Name |
| Any internal name to label your connection |
Dataset ID |
| The ID of your BigQuery dataset (see below) |
Service account JSON |
| Full JSON credentials file for a service account with appropriate permissions |
Retrieve the dataset ID
Log into the Google Cloud Console
Go to BigQuery
Select the dataset that contains the tables to be checked
Copy the Dataset ID
The dataset ID uniquely identifies the group of tables for data checks
Create the service account JSON
If you don’t already have a service account with the required permissions, follow these steps:
Step 1: Add a Service Account (Optional)
Go to IAM & Admin > Service Accounts
Click Create Service Account
Enter a name and click Continue
Add a dedicated service account for the DQC Platform
Step 2: Assign Permissions
Add the following three roles under product “BigQuery”:
BigQuery Data Viewer
BigQuery Job User
BigQuery Read Session User
These roles grant safe, read-only access to your data
Step 3: Generate JSON Key
Select the new service account
Go to the Keys tab
Click Add Key > Create New Key > JSON
Download the file
Open the file in a text editor and copy the full JSON content
Paste this into the Service account JSON field in the DQC Platform
The key allows secure automated access via the DQC Platform
Enable BigQuery API (if not yet enabled)
Before using the connector, ensure the BigQuery API is activated in your Google Cloud project.
Search for “BigQuery API” in the GCP console and click Enable
Allow Static IP Access
3.123.94.228Troubleshooting
When DQC cannot connect to BigQuery or load its tables, it shows the reason with a short fix and links to this section. Look up the beginning of the message:
Message in DQC | Likely cause | Fix |
|---|---|---|
| The dataset ID is wrong or belongs to another project than the service account | Enter the dataset ID as shown in BigQuery (see Retrieve the dataset ID) |
| The project in the service account JSON does not exist | Create the key in the project that holds the dataset |
| The service account lacks a BigQuery role | Assign BigQuery Data Viewer and BigQuery Job User (see Assign Permissions) |
| The BigQuery API is off | Enable the BigQuery API (see Enable BigQuery API) |
| The key was deleted or disabled | Create a new JSON key and paste it |
| The service account JSON is incomplete or not valid JSON | Paste the complete downloaded key file |
| The table was renamed, moved or deleted, or the user lost access to it after the last sync | Restore the table or the access, then resync the connector |
Synchronization failed: when a sync cannot connect, the connector shows Failed on the Data sources screen and the badge links to this section. Edit the connector and click Load tables or Save: DQC tests the connection again and shows the current reason.
Connection test passes, but tables do not load: reading data needs BigQuery Job User in addition to BigQuery Data Viewer.
Still stuck? Write to support@dqc.ai with the connector name, the time of the attempt and the full message.
Notes
The service account must be tied to the same project as the dataset
Permissions are read-only — no changes to data are made
Learn more: Supported data sources, Connection to Azure SQL, Data source access permissions