CAPACITY_COMMITMENTS view

TheINFORMATION_SCHEMA.CAPACITY_COMMITMENTS view contains a near real-timelist of all current capacity commitments within the administration project. Eachrow represents a single, current capacity commitment. A current capacitycommitment is either pending or active and has not been deleted. For moreinformation about reservation, seeSlot commitments.

Note: The view namesINFORMATION_SCHEMA.CAPACITY_COMMITMENTS andINFORMATION_SCHEMA.CAPACITY_COMMITMENTS_BY_PROJECT are synonymous and can beused interchangeably.

Required permission

To query theINFORMATION_SCHEMA.CAPACITY_COMMITMENTS view,you need thebigquery.capacityCommitments.list Identity and Access Management (IAM)permission for the project.Each of the following predefined IAM roles includes the requiredpermission:

  • roles/bigquery.resourceAdmin
  • roles/bigquery.resourceEditor
  • roles/bigquery.resourceViewer
  • roles/bigquery.user
  • roles/bigquery.admin

For more information about BigQuery permissions, seeAccess control with IAM

Schema

TheINFORMATION_SCHEMA.CAPACITY_COMMITMENTS view has thefollowing schema:

Column nameData typeValue
ddlSTRINGThe DDL statement used to create this capacity commitment.
project_idSTRINGID of the administration project.
project_numberINTEGERNumber of the administration project.
capacity_commitment_idSTRINGID that uniquely identifies the capacity commitment.
commitment_planSTRINGCommitment plan of the capacity commitment.
stateSTRINGState the capacity commitment is in. Can bePENDING orACTIVE.
slot_countINTEGERSlot count associated with the capacity commitment.
editionSTRINGThe edition associated with this reservation. For more information about editions, seeIntroduction to BigQuery editions.
is_flat_rateBOOLWhether the commitment is associated with the legacy flat-rate capacity model or an edition. IfFALSE, the current commitment is associated with an edition. IfTRUE, the commitment is the legacy flat-rate capacity model.
renewal_planSTRINGNew commitment plan after the end of current commitment plan. You can change the renewal plan for a commitment at any time until it expires.

For stability, we recommend that you explicitly list columns in your information schema queries instead ofusing a wildcard (SELECT *). Explicitly listing columns prevents queries frombreaking if the underlying schema changes.

Scope and syntax

Queries against this view must include aregion qualifier.If you don't specify a regional qualifier, metadata is retrieved from allregions. The following table explains the region scope for this view:

View nameResource scopeRegion scope
[PROJECT_ID.]`region-REGION`.INFORMATION_SCHEMA.CAPACITY_COMMITMENTS[_BY_PROJECT]Project levelREGION
Replace the following:
  • Optional:PROJECT_ID: the ID of your Google Cloud project. If not specified, the default project is used.
  • REGION: anydataset region name. For example,`region-us`.

    Note: You must usea region qualifier to queryINFORMATION_SCHEMA views. The location of the query execution must match the region of theINFORMATION_SCHEMA view.

Example

The following example returns a list of active capacity commitments for thecurrent project:

SELECTcapacity_commitment_id,slot_countFROM`region-us`.INFORMATION_SCHEMA.CAPACITY_COMMITMENTSWHEREstate='ACTIVE';

The result is similar to the following:

+------------------------+------------+| capacity_commitment_id | slot_count |+------------------------+------------+|    my_commitment_05    |    1000    ||    my_commitment_06    |    1000    ||    my_commitment_07    |    1500    ||    my_commitment_08    |    2000    |+------------------------+------------+

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2026-02-19 UTC.