BigQuery Integration

Connect Querri to Google BigQuery, choose the tables to load, and ask questions about them in plain language.

Overview

BigQuery connects with Google sign-in. Each connector reads one Google Cloud project: you pick the project, choose its tables, and Querri copies them into its own storage.

Querri answers questions from that copy. Asking a question doesn’t run a query in BigQuery; your project only does work while tables sync.

Before you start

• A Google account with access to a BigQuery project and its tables
• Pop-ups allowed for Querri, since Google’s sign-in opens in its own window

Connecting BigQuery

1. Click Connect in the app rail to open Add data, and pick BigQuery. Admins can also click Connect on it in Settings → Connectors.
2. Google’s sign-in window opens. Sign in and approve access.
3. The connector dialog opens. Under Select BigQuery Project, choose a project: “Choose which BigQuery project to access. One connector per project.”
4. Choose the tables to load. There’s no separate dataset step.
5. If you need them, add Custom SQL Queries to load a query’s result as its own source. Test Query (LIMIT 10) checks a query on 10 rows.
6. Check Limit total rows per table. It’s on at 100,000 rows by default (“Recommended: 100,000 rows for testing”). Turn it off to load every row. The form then suggests granting the BigQuery User role, which makes full loads much faster.
7. Click Save and Load Data. A progress card shows each table loading, then offers View in Library and Sync daily.

Caution

Pressing Enter in the dialog saves it, so finish your choices first.

The connector lands in the workspace you’re in if you’re a member of it, or in your private workspace otherwise.

More than one project

Each connector reads one project. For another project, add another BigQuery connector with the add-another icon on its card in Settings → Connectors, and give each one a name you’ll recognize, such as “BigQuery: Marketing”.

Working with BigQuery data

Each table you load becomes a source in your Library, typed Dataset. Ask about it as you would any other source:

• “Show the top 10 products by revenue last quarter.”
• “What’s our monthly revenue growth this year?”
• “Compare this month’s signups with last month’s.”

Because Querri works from the synced copy:

• Partitioning and clustering affect how fast tables sync, not how fast Querri answers.
• To keep loads small, choose only the tables you need, keep a row limit, or load a custom query that filters to recent data.
• Syncs read from your BigQuery project, so any BigQuery charges for those reads go to your Google Cloud billing. See BigQuery pricing.

Sync scheduling

The connector’s owner can keep BigQuery data up to date on the Schedule tab, with Full Refresh, Incremental, or both. For incremental syncs, set Cursor Field to a TIMESTAMP or DATETIME column that changes whenever a row does, such as updated_at. Tables without that column are skipped by the incremental schedule.

A common setup is an incremental schedule Every Day and a full refresh Every Week. Scheduled syncs use credits when they run; syncs you start by hand don’t. See Sync Scheduling.

Google Workspace: repeated sign-in prompts

With a Google Workspace account, your organization’s Google Cloud session control can make sign-in expire on a timer. When that happens, the connector shows Reauthentication needed and asks you to sign in again. Personal Gmail accounts aren’t affected.

For Google Workspace admins

A Super Admin or Security Admin can let Querri’s sign-in last longer.

Step 1: Mark the app as trusted

1. Go to admin.google.com.
2. Open Security → Access and data control → API controls.
3. Find Querri’s app in the list, and click Change access.
4. Choose Trusted, and save.

According to Google’s documentation, trusting an app doesn’t give it more access. The app is still limited to the access it asked for.

Step 2: Exempt trusted apps from reauthentication

1. In the Admin console, open Security → Access and data control → Google Cloud session control.
2. Tick Exempt trusted apps, and save.

Changes can take a while to apply. See Set session length for Google Cloud services. Google offers this exemption only in some Workspace editions. If yours doesn’t have it, you can lengthen the reauthentication interval in the same settings instead.

Step 3: Sign in again

Once the changes apply, open the BigQuery connector and click Reauthenticate. Don’t disconnect and reconnect: disconnecting deletes the data the connector synced.

Asking your IT team

If you’re not a Workspace admin, you can send your IT team something like this:

Subject: Please exempt Querri's BigQuery sign-in from session control

Hi,

I use Querri with BigQuery, and our Google Cloud session control makes me
sign in again regularly. Could you make these two changes?

1. Admin console > Security > Access and data control > API controls:
   find Querri's app, choose Change access, and set it to Trusted.
   Per Google (https://support.google.com/a/answer/7281227), this doesn't
   give the app more access; it only exempts it from reauthentication.

2. Admin console > Security > Access and data control > Google Cloud session
   control: tick "Exempt trusted apps" and save.
   (https://support.google.com/a/answer/9368756)

Once that's done, I'll reauthenticate the connector in Querri.

Thanks!

Troubleshooting

Frequent sign-in prompts

See Google Workspace: repeated sign-in prompts.

Sign-in fails

• Allow pop-ups for Querri.
• Check that the BigQuery API is enabled in your Google Cloud project.
• Check whether your organization’s Google policies block third-party apps.

No projects in the list

• Check that you signed in with the Google account that has access to the project.
• To use a different Google account, add another BigQuery connector.

Tables are missing, or loads fail with a permission error

• Check that your account can read the dataset and tables in BigQuery.
• Ask your Google Cloud administrator for access if you’re on a company account.

Only part of a table loaded

Limit total rows per table is on at 100,000 rows by default. Raise it or turn it off, then click Save and Load Data.

Loads are slow

• Load fewer tables, or keep a row limit.
• Load a custom query that filters to the rows you need.
• Grant the BigQuery User role, which the form suggests for loads without a row limit.

”Quota exceeded”

BigQuery limits how much work a project can do at once. Wait a few minutes and sync again, and check your quotas in the Google Cloud console.

Disconnecting BigQuery

In Querri:

1. Open the connector and click Disconnect, followed by its name.
2. Confirm. Querri deletes the connector, the tables it synced, and everyone’s access to them.

In Google:

1. Go to myaccount.google.com/permissions.
2. Find Querri in your connected apps.
3. Remove its access.

Next Steps

• Connecting Databases: the other database connectors
• Sync Scheduling: full and incremental schedules
• Managing Connections: change, refresh and remove connectors

Additional Resources

• BigQuery documentation: cloud.google.com/bigquery/docs
• BigQuery pricing: cloud.google.com/bigquery/pricing
• BigQuery best practices: cloud.google.com/bigquery/docs/best-practices