A faster BigQuery client than DBeaver.

Three real pain points

The cold start. DBeaver runs on the JVM, and every launch pays a startup tax you feel every single morning, even on a fast Mac. QueryFlow launches like a native app, because it is one.

Generic SQL handling. DBeaver's editor treats BigQuery mostly like any other JDBC source. GoogleSQL specifics, backtick-quoted project.dataset.table paths, UNNEST, STRUCT, don't get the same first-class autocomplete you'd expect from a client built around the dialect.

No AI panel without add-ons. Asking a question in plain English and getting back working GoogleSQL against your real tables isn't part of DBeaver's core experience.

Feature comparison

Where DBeaver still wins

DBeaver's connector list is enormous, dozens of databases through community drivers, and it's free and open source. If you need to connect to something obscure that QueryFlow doesn't support, or you want a no-cost tool and don't mind the JVM tradeoffs, DBeaver is a reasonable choice. This isn't a case for uninstalling it entirely, just for not using it as your daily BigQuery driver if speed and dialect handling matter to you.

A worked example

A query that flattens a repeated field, the kind of thing generic SQL editors autocomplete badly:

SELECT customer_id, item.sku, item.quantity
FROM `my-gcp-project.orders.line_items`,
  UNNEST(items) AS item
WHERE item.quantity > 1;

In QueryFlow, item.sku and item.quantity autocomplete correctly because the editor understands the struct's shape. That's a small thing that saves real time across a hundred queries a week.

Honest migration note

Switching means re-adding your BigQuery connection by hand, sign in with Google or paste your service account key again. There's no automatic import from DBeaver's connection list. Saved queries you want to keep need to be copied over manually too; there's no bulk migration tool.

If you keep both installed

Plenty of people don't fully switch on day one. Keep DBeaver around for the odd niche database it supports that QueryFlow doesn't, and use QueryFlow for the BigQuery work you do daily. There's no conflict in running both; they're separate apps pointed at the same warehouse, and nothing about connecting through one affects the other.

A word on cost, either way

Neither client changes what BigQuery bills you. Cost is driven by bytes scanned, not which SQL editor submitted the query, so a habit of running SELECT * against a huge table costs the same whether it came from DBeaver, the Console, or QueryFlow. Whichever client you land on, the query itself is still where cost discipline matters.

Keeping both around during the switch

You don't need to delete DBeaver the day you start QueryFlow. Run both for a week or two against the same project, compare results on a query you already trust, and let the daily habit shift on its own rather than forcing a hard cutover before you're sure the new editor covers everything you need.

What actually carries over on day one

Nothing automatic, your Project ID and either a Google login or a service account key are all you need to reconnect. If you've been maintaining a personal library of saved DBeaver scripts, plan on an afternoon of copying the ones you actually still use rather than trying to migrate everything at once.

A reasonable order to do it in

Start with the queries you run daily, not the ones you might need someday. Get those working in QueryFlow first, confirm the results match what DBeaver gave you, and only then go back for anything less frequently used. That order gets you productive in the new client fastest, with the least-used queries left for whenever you actually need them again.

What the Ask panel can help with here

If a query you're porting over is complex enough that retyping it from a DBeaver export feels error-prone, paste the SQL into a scratch tab and ask the panel to explain what it does before you trust it's correct in the new environment. It's a quick sanity check, not a substitute for actually reading the query yourself.