Google Cloud Update August ’25: Daily usage limit for BigQuery projects

Get updates as soon as we post them

Latest news, tips and tricks, straight to your inbox

Teams often harness the incredible power of BigQuery to unlock business insights. Its on-demand pricing model is a key feature, offering amazing flexibility. However, with that flexibility comes the responsibility of managing costs, and a single large query can sometimes lead to unexpected expenses.

To help you gain more predictable control over your analytics spending, Google Cloud is implementing a pivotal change to how on-demand query costs are managed. This isn’t just a technical update; it’s a strategic shift towards proactive financial governance. Let’s dive into this upcoming change, effective September 1, 2025, and explore how you can leverage it to master your BigQuery costs.

Why is This Quota Change So Important?

Implementing a default daily usage quota might seem like a small adjustment, but its impact on financial governance is significant. This change is critical because it helps you:

  1. Prevent Bill Shock: It establishes a crucial safety net, preventing a miswritten script or an unexpectedly large ad-hoc query from causing significant, accidental cost overruns.
  2. Enforce Financial Governance: By setting explicit limits, you can align your cloud usage directly with your budget, making spending more predictable and manageable.
  3. Improve Budget Predictability: Knowing there’s a ceiling on daily on-demand spend allows for more accurate forecasting of your analytics costs.
  4. Encourage Cost-Conscious Practices: The presence of a quota naturally encourages teams to write more efficient queries and to be more mindful of the data they are processing.

Breaking Down the Changes: What You Need to Know

This update centers on two key quotas: QueryUsagePerDay (total data processed per project per day) and QueryUsagePerUserPerDay. Here’s a clear breakdown of what’s happening.

What’s Changing:

    • Quotas Will Apply  These daily limits will now only affect queries running under the on-demand pricing model. If you are using BigQuery Reservations (flat-rate pricing), your workloads will be exempt from these quotas, ensuring consistency for your dedicated capacity.
  • A New Default for New Projects: All Google Cloud projects created after September 1, 2025, will automatically have a default QueryUsagePerDay limit of 200 TiB. This provides a baseline of cost protection from day one.
  • “Smart Limits” for Existing “Unlimited” Projects: If your current projects are set to “unlimited” for these quotas, they will be automatically updated to a new custom limit. This limit is intelligently derived from your project’s peak usage over the last 30 days, with additional headroom to accommodate growth. This data-driven approach minimizes disruption by aligning the new limit with your established usage patterns.

What Stays the Same:

    • Your Existing Custom Limits are Unchanged: If you have already configured a specific numeric value for your daily quotas, no changes will be made. Your proactive settings will be fully respected.
  • You Remain in Full Control: This update does not remove your ability to manage quotas. You can still adjust these limits up or down at any time via the Google Cloud Console, Cloud Quotas API, or gcloud CLI to fit your specific needs.

Best Practices for a Smooth Transition

To ensure your BigQuery workloads continue running seamlessly, we strongly recommend taking the following actionable steps before the September 1, 2025 deadline:

  • Analyze Your Current On-Demand Usage: First, understand your baseline. Use Cloud Billing reports or query BigQuery’s INFORMATION_SCHEMA to determine your average and peak daily on-demand query processing volume. This data is essential for making an informed decision.
  • Review and Proactively Set Limits: Navigate to the IAM & Admin > Quotas page in your Google Cloud Console. Find the QueryUsagePerDay limit for the BigQuery API. If it currently says “unlimited,” take this opportunity to set an explicit limit that aligns with your budget and expected workload.
  1. Create Proactive Usage Alerts: A quota shouldn’t be a silent failure point. Use Cloud Monitoring to create alerts that notify you when your usage hits 50%, 75%, and 90% of its daily limit. This transforms the quota from a hard stop into an early warning system, giving you time to optimize queries or adjust the limit if needed.
  2. Evaluate Your Pricing Model: If your on-demand usage is consistently high and predictable, this may be a good time to evaluate BigQuery Reservations. Migrating high-volume workloads to a flat-rate model can be more cost-effective and completely removes concerns about on-demand query quotas.

Ready to Master Your BigQuery Costs?

This upcoming change is a powerful step towards making BigQuery costs more predictable and controllable for everyone. By embracing these tools, you can move from reactively analyzing your monthly bill to proactively managing your daily cloud spend.

We encourage you to review your project quotas and set up monitoring alerts today. Taking these simple, proactive steps will ensure a smooth transition and empower you with greater financial control over your data analytics environment.

If you have any questions or require assistance in preparing for this change, please don’t hesitate to reach out to our team at Pawa IT. We are here to help you navigate these updates and optimize your Google Cloud environment.