BigQuery
Last updated
Last updated
IP RESTRICTIONS
Make sure to allow traffic from one of the Paradime IPs in your firewall depending on the data location selected.
👉 See also: Paradime IP addresses.
This set of permissions will enable users in Paradime to read from and create tables and views when running dbt™️ from the Paradime terminal in you BigQuery project.
You will be prompted to add a Development connection during the onboarding, or you can add more connections by going to account settings > connections, select Development Environment and enter the required fields.
Check our Tutorial on how to setup BigQuery OAuth in your BIgQuery account. Once this connection is configured, each user will be redirected to BigQuery and asked to approved the required scopes.
Below are list of fields and example to create a connection.
🏢 Workspace level fields are set by the the workspace Admin and not configurable for by user
👥 User level fields are set by each user (Admin/Developer) when setting the Development connection.
Profile Name
dbt-bigquery
Target
dev
Dataset Location
The location of BigQuery datasets can be configured using the location configuration in a BigQuery profile.
US
Project ID
dbt-demo-project
Client ID
The Client ID generated when setting up the OAuth credentials.
xyz123.apps.googleusercontent.com
Client Secret
The Client Secret generated when setting up the OAuth credentials.
GOCSPX-hPfGJe7sd238772BLBA2Bi0ds
Execution Project ID (Optional)
(Optional) analytics-global-project
Dataset
The default dataset used to build dbt™️ objects at runtime.
dbt_john
Threads
8
Uploading a service account JSON key file is the quickly and accurately way to configure a connection to BigQuery and authenticate each user's development credentials.
To create a service account in BigQuery, follow the detailed steps in Google Cloud's Creating and managing service account keys.
Below are list of fields and example to create a connection.
🏢 Workspace level fields are set by the the workspace Admin and not configurable for by user
👥 User level fields are set by each user (Admin/Developer) when setting the Development connection.
Profile Name
dbt-bigquery
Target
dev
Dataset Location
The location of BigQuery datasets can be configured using the location configuration in a BigQuery profile.
US
Service AccountService Account JSON
The service account JSON file created for this service user.
service_account_user.json
Execution Project ID (Optional)
(Optional) analytics-global-project
Dataset
The default dataset used to build dbt™️ objects at runtime.
dbt_john
Threads
8
The profile name set in your dbt_project.yaml . See more .
The target name used to identify the connection. See more .
Location can be either a multi-regional location (e.g. EU, US), or a regional location (e.g. europe-west2 ). See more .
The unique identifier of your BigQuery project. See more .
You can specify an Execution Project ID to bill for query execution, instead of the project where you materialize your resources. See more .
The number of threads used in this connection. See more .
The profile name set in your dbt_project.yaml . See more .
The target name used to identify the connection. See more .
Location can be either a multi-regional location (e.g. EU, US), or a regional location (e.g. europe-west2 ). See more .
You can specify an Execution Project ID to bill for query execution, instead of the project where you materialize your resources. See more .
The number of threads used in this connection. See more .
