Creates a JDBC connection so you can run BigQuery SQL from the DBeaver IDE.
Running BigQuery from DBeaver lets engineers keep a single, keyboard-driven IDE while gaining autocomplete, ER diagrams, and result exports without leaving the desktop.
Click Database ▸ New Database Connection ▸ BigQuery. If the BigQuery driver is missing, DBeaver offers to download it automatically.
DBeaver uses the Simba JDBC driver. The URL template is:jdbc:bigquery://https://www.googleapis.com/bigquery/v2:443;ProjectId=<PROJECT_ID>;OAuthType=3;
For interactive desktop use, pick OAuth 2.0 Installed Application. For service accounts, paste the JSON key and select OAuth Service Account.
After filling in credentials, press Test Connection. You should see "Connected" along with driver and project details. Click Finish to save the profile.
Open a new SQL editor, choose the BigQuery connection, and run familiar SQL. Autocomplete exposes datasets, tables, and columns.
SELECT c.name, SUM(oi.quantity * p.price) AS lifetime_valueFROM `shop.Customers` cJOIN `shop.Orders` o ON o.customer_id = c.idJOIN `shop.OrderItems` oi ON oi.order_id = o.idJOIN `shop.Products` p ON p.id = oi.product_idGROUP BY c.nameORDER BY lifetime_value DESC;
Enable Query Results ▸ Save to Local Cache to avoid re-billing for re-runs. Always preview a dataset’s row count before SELECT *
to control costs.
403 errors usually mean the service account lacks bigquery.readsessions.create
. Garfield 404 indicates an incorrect ProjectId
in the JDBC URL.
Yes. Simba’s JDBC driver ships under the Apache 2.0 license and DBeaver downloads it automatically.
Absolutely. Choose OAuthType 2, provide the JSON key, and make sure the account has BigQuery User roles.
Yes. Enable local result caching to avoid re-running cost-incurring queries.