Forum Discussion
Big Qyery Direct Query Error
- 10 months ago
Hi amilpbi
The message shown is a Quota Exceeded error in BigQuery, error code 403.
Meaning: the queries Power BI generates in DirectQuery mode have exceeded the Free Tier quota or the quota defined for the BigQuery project (amount of bytes scanned per month).The cause:
-
DirectQuery does not pre-aggregate but instead fires queries directly to BigQuery for every report interaction.
-
With datasets of ~10GB or more, every filter or slice in Power BI scans a large amount of rows, which quickly burns through the scan quota.
Root of the problem
-
Not a Power BI technical bug, but a BigQuery limitation when used with DirectQuery.
-
Free Tier gives only 1TB of query scans per month. With raw Google Analytics export tables, this is consumed very quickly.
-
Without advanced IAM permissions, it’s hard to set up ETL that aggregates the data beforehand.
Possible solutions
-
Switch from DirectQuery to Import:
-
Not feasible to import the full 10GB, but you can:
-
Build reduced tables in BigQuery (partitioned/aggregated).
-
Import only the required aggregations into Power BI instead of the raw events.
-
-
-
Materialized Views or intermediate tables in BigQuery:
-
Create views that pre-calculate metrics like “avg time per user per module” or “articles clicked.”
-
Point Power BI to these smaller tables instead of the raw export.
-
-
Partitioning & Clustering:
-
If staying on DirectQuery, partition by Date and cluster by User ID/Module.
-
This greatly reduces bytes scanned for each query.
-
-
Dataflows or external ETL (Power BI Dataflows, Fabric, or other ETL tool):
-
Pull only the required fields from GA Export, not the entire dataset.
-
Store daily/monthly aggregations.
-
-
Upgrade BigQuery Billing:
-
On Free Tier alone, there is no full solution. A paid project is required to avoid constant query failures.
-
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly
-
Hi amilpbi,
Just checking in to see if the issue has been resolved on your end. If the earlier suggestions helped, that’s great to hear! And if you’re still facing challenges, feel free to share more details happy to assist further.
Thank you.
Hi amilpbi,
Hope you had a chance to try out the solution shared earlier. Let us know if anything needs further clarification or if there's an update from your side always here to help.
Thank you.
- v-kpoloju-msft10 months agoCommunity Support
Hi amilpbi,
Just wanted to follow up one last time. If the shared guidance worked for you, that’s wonderful hopefully it also helps others looking for similar answers. If there’s anything else you'd like to explore or clarify, don’t hesitate to reach out.Thank you.