# BigQuery

{% hint style="warning" %}
**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](https://docs.paradime.io/app-help/developers/ip-restrictions).
{% endhint %}

{% hint style="info" %}
We advise creating a new BigQuery Service Account and grant the suggested access required to create tables and views your Production BigQuery project.
{% endhint %}

## Create a service account <a href="#create-a-service-account-0-0" id="create-a-service-account-0-0"></a>

To create a service account in BigQuery, follow the detailed steps in [Google Cloud's Creating and managing service account keys](https://cloud.google.com/iam/docs/creating-managing-service-account-keys#iam-service-account-keys-delete-console).

### Required permissions

This set of permissions will enable Paradime to read from and create tables and views when running production jobs in you BigQuery project.

```
BigQuery Data Editor
BigQuery User
```

## Add Scheduler Connection

To add the BigQuery Production connection, follow these instructions:&#x20;

1. Click **Settings** in the top menu bar of the Paradime interface to access **Account Settings**
2. In the left sidebar, click "**Connections**"
3. Click "**Add New**" next to the **Bolt Schedules** section
4. Select "**Bigquery**"

<figure><img src="https://2337193041-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHET0AD04uHMgdeLAjptq%2Fuploads%2F57ntB5vIQ6b2jJEn2PQL%2Fprod_connection_bigquery_sajson.png?alt=media&#x26;token=1a0a11de-d5a6-48c8-895f-769f14675e79" alt="" width="540"><figcaption></figcaption></figure>

### Fields Details

Below are list of fields and example to create a connection.

<table><thead><tr><th width="180.33333333333331">Field</th><th width="352">Description</th><th>Example</th></tr></thead><tbody><tr><td>Profile Name</td><td>The profile name set in your <code>dbt_project.yaml</code> . See more <a href="https://docs.getdbt.com/docs/core/connect-data-platform/connection-profiles">here</a>.</td><td><strong><code>dbt-bigquery</code></strong></td></tr><tr><td>Target</td><td>The target name used to identify the connection. See more <a href="https://docs.getdbt.com/reference/dbt-jinja-functions/target">here</a>.</td><td><strong><code>prod</code></strong></td></tr><tr><td>Dataset Location</td><td><p>The location of BigQuery datasets can be configured using the location configuration in a BigQuery profile. </p><p></p><p>Location can be either a multi-regional location (e.g. <code>EU</code>, <code>US</code>), or a regional location (e.g. <code>europe-west2</code> ). See more <a href="https://cloud.google.com/bigquery/docs/locations">here</a>.</p></td><td><strong><code>US</code></strong></td></tr><tr><td>Service AccountService Account JSON</td><td>The service account JSON file created for this service user.</td><td><strong><code>service_account_user.json</code></strong></td></tr><tr><td>Execution Project ID (Optional)</td><td>You can specify an Execution Project ID to bill for query execution, instead of the project where you materialize your resources. See more <a href="https://docs.getdbt.com/docs/core/connect-data-platform/bigquery-setup#execution-project">here</a>.</td><td>(Optional) <strong><code>analytics-global-project</code></strong></td></tr><tr><td>Dataset</td><td>The default dataset used to build dbt™️ objects at runtime.</td><td><strong><code>dbt_prod</code></strong></td></tr><tr><td>Threads</td><td>The number of threads used in this connection. See more <a href="https://docs.getdbt.com/docs/running-a-dbt-project/using-threads">here</a>.</td><td><strong><code>8</code></strong></td></tr></tbody></table>