Two BigQuery changes this month help teams that share capacity. On 11 November 2026, project caps became generally available, and on 9 November compute cost attribution entered preview.
What's new
- Project caps (generally available): set a maximum number of slots and a maximum concurrency for each project inside a BigQuery reservation. Available on the Enterprise and Enterprise Plus editions.
- Compute cost attribution (preview): an opt-in setting that charges compute costs to the projects that run the queries, rather than to the project that owns the reservation.
Is BigQuery costing more than it should?
We review your queries, storage, slots and cost controls, then give you quick wins and a plan.
Why it matters for your business
When several teams share one reservation, a single heavy dashboard or runaway query can slow everyone down, and the bill lands on whoever owns the reservation. Caps keep one project from crowding out the rest. Cost attribution answers the question finance always asks: which team actually used the money?
If you're on BigQuery's on-demand pricing rather than an edition with reservations, these features don't apply yet. The question behind them still does: do you know what each workload costs?
How D3V can help
- Our free BigQuery health check reviews your queries, storage, slots and cost controls, then gives you quick wins and a plan.
- We can set up reservations, caps and cost attribution so spend is visible by team (data & analytics).
- Zenta Pulse tracks daily spend by project and service and alerts you when it spikes.
Source: BigQuery release notes, Google Cloud.
