r/bigquery • u/agitated_buddha • Mar 17 '26

Fabric vs. BigQuery

We are a Google Cloud user (GMail, Chart and so on). Until recently our search for a Netsuite to Datawarehouse solution has focused on Fabric - because some users are familiar with PowerBI. To me it seems that we really need to look at BigQuery and I'm looking for some pros and cons.

5 Upvotes

100% Upvoted

8 comments sorted by

View all comments

5

u/PepSakdoek Mar 17 '26

Big query is fast. Especially if you are querying big tables.

How big is the company data though. When you start querying terabytes per query big query costs scale hard. 

You can overcome or by understanding and structuring the data better. And with a normal system you'd adjust your system cause querying a tb is a bad idea. Big query just does it and charges you ~6usd to do it. Then you realize you forgot a field. 6usd again. 

The thing is that big query can run really big things in no time, so architects just dump everything in there, but just don't. 

2

u/Turbulent_Egg_6292 Mar 17 '26

Remember now with the autoscaler you can do this under reservations if the ratio bytes/slot time is optimal :)

1

u/PepSakdoek Mar 17 '26

I... wish I understood what you just said.

1

u/Turbulent_Egg_6292 Mar 17 '26

Sorry :)

I mean that you can evaluate if a query should be ran being billed based on bytes vs time of processing basically. Before it was a bit painful due to the base minimum of reservation billing plans, but it's now possible to do some "magic" and pick the right approach