Purchase and manage legacy slot commitments
The BigQuery Reservation API lets you purchase dedicated slots (called commitments), create pools of slots (called reservations), and assign projects, folders, and organizations to those reservations.
A capacity commitment is a purchase of BigQuery compute capacity for some minimum duration of time. Purchasing a capacity commitment is optional when creating a reservation with an edition, but can provide cost savings.
Commitments are a regional resource. Commitments purchased in one region or multi-region cannot be used in any other regions or multi-regions. Commitments cannot be moved between regions or between regions and multi-regions.
Enable the Reservations API
The BigQuery Reservation API is distinct from the existing BigQuery API and must be enabled independently. For more information, see Enabling and disabling APIs.
- The name of the API is "BigQuery Reservations API"
- The endpoint for the BigQuery Reservation API is
bigqueryreservation.googleapis.com
.
![Enable API.](https://cloud.google.com/static/bigquery/images/reservations-enable-api.png?authuser=1)
Purchase slots
To reserve capacity for some minimum amount of time, you can purchase a capacity commitment. This provides a discount and saves on costs. For more information about the specific costs, see BigQuery pricing.
Required permissions
To create a capacity commitment, you need the following Identity and Access Management (IAM) permission:
bigquery.capacityCommitments.create
on the administration project that maintains ownership of the commitments.
Each of the following predefined IAM roles includes this permission:
BigQuery Admin
BigQuery Resource Admin
For more information about IAM roles in BigQuery, see Predefined roles and permissions.
Create a capacity commitment
Commitments are a regional resource. Commitments purchased in one region or multi-region cannot be used in any other regions or multi-regions. Commitments cannot be moved between regions or between regions and multi-regions.
Console
In the Google Cloud console, go to the BigQuery page.
In the navigation panel, go to the Capacity management section.
Click Create Commitment.
Under Configure:
- Select the location.
- In the Capacity model section, select the capacity model.
- Select the Commitment duration, which specifies your commitment plan.
If you are purchasing an Annual commitment, select the Renewal plan that you want to take effect when the commitment expires:
- Do not renew and convert to a monthly commitment (Default). When the annual commitment expires, it converts to a monthly commitment.
- Renew annually. When the annual commitment expires, it renews for another year as an annual commitment.
- Do not renew and convert to flex slots. When the annual commitment expires, it converts to a flex slots commitment.
For more information, see Commitments.
Enter the Number of slots you want to purchase.
Click Next.
Review the Cost estimate for your purchase.
Under Confirm and submit:
- Type CONFIRM to confirm the purchase.
- Click Purchase to purchase the slots.
To view the commitment, click View slot commitments. After the capacity is provisioned, the requested capacity commitment has a green status.
The first time you purchase capacity, a default
reservation is created.
SQL
To create a capacity commitment, use the
CREATE CAPACITY
DDL statement.
In the Google Cloud console, go to the BigQuery page.
In the query editor, enter the following statement:
CREATE CAPACITY `ADMIN_PROJECT_ID.region-LOCATION.COMMITMENT_ID` OPTIONS ( slot_count = NUMBER_OF_SLOTS, plan = 'PLAN_TYPE');
Replace the following:
ADMIN_PROJECT_ID
: the project ID of the administration project that will maintain ownership of this commitmentLOCATION
: the location of the commitmentCOMMITMENT_ID
: the ID of the commitmentIt must be unique to the project and location. It must start and end with a lowercase letter or a number and contain only lowercase letters, numbers, and dashes.
NUMBER_OF_SLOTS
: the number of slots to purchasePLAN_TYPE
: the plan type, such asFLEX
,MONTHLY
, orANNUAL
.
Click
Run.
For more information about how to run queries, see Run an interactive query.
bq
Use the bq mk
command
with the
--capacity_commitment
flag
to purchase slots.
bq mk \ --project_id=ADMIN_PROJECT_ID \ --location=LOCATION \ --capacity_commitment=true \ --plan=PLAN_TYPE \ --slots=NUMBER_OF_SLOTS
Replace the following:
ADMIN_PROJECT_ID
: the project ID of the administration project that will maintain ownership this commitmentLOCATION
: the location of the commitmentPLAN_TYPE
: the plan type, such asFLEX
,MONTHLY
, orANNUAL
.NUMBER_OF_SLOTS
: the number of slots to purchase.
View capacity commitments
Required permissions
To view commitments, you need the following Identity and Access Management (IAM) permission:
bigquery.capacityCommitments.list
on the administration project that maintains ownership of the commitments.
Each of the following predefined IAM roles includes this permission:
BigQuery Admin
BigQuery Resource Admin
BigQuery Resource Editor
BigQuery Resource Viewer
BigQuery User
For more information about IAM roles in BigQuery, see Predefined roles and permissions.
View capacity commitments by project
To view your capacity commitments by project:
Console
In the Google Cloud console, go to the BigQuery page.
In the navigation panel, go to the Capacity Management section.
Click the Slot commitments tab. Your capacity commitments are listed in the table under Commitments.
SQL
To view the commitments for an administration project, query the
INFORMATION_SCHEMA.CAPACITY_COMMITMENTS_BY_PROJECT
view.
In the Google Cloud console, go to the BigQuery page.
In the query editor, enter the following statement:
SELECT capacity_commitment_id FROM `region-LOCATION`.INFORMATION_SCHEMA.CAPACITY_COMMITMENTS_BY_PROJECT WHERE project_id = 'ADMIN_PROJECT_ID' AND slot_count = 100;
Replace the following:
LOCATION
: the location of the commitmentsADMIN_PROJECT_ID
: the project ID of the administration project that owns the commitments
Click
Run.
For more information about how to run queries, see Run an interactive query.
bq
Use the bq ls
command
with the
--capacity_commitment
flag
to list the commitments for an administration project.
bq ls \ --capacity_commitment=true \ --location=LOCATION \ --project_id=ADMIN_PROJECT_ID
Replace the following:
LOCATION
: the location of the commitmentsADMIN_PROJECT_ID
: the project ID of the administration project that owns the commitments
Update capacity commitments
You can make the following updates to a capacity commitment:
- Renew an existing commitment.
- Convert a commitment to a commitment plan with a longer duration.
- Split a commitment into two commitments.
- Merge two commitments into a single commitment.
Required permissions
To update capacity commitments, you need the following Identity and Access Management (IAM) permission:
bigquery.capacityCommitments.update
on the administration project that maintains ownership of the commitments.
Each of the following predefined IAM roles includes this permission:
BigQuery Admin
BigQuery Resource Admin
For more information about IAM roles in BigQuery, see Predefined roles and permissions.
Renew a commitment
Annual commitments have a renewal plan, which you specify when you create or convert to an annual commitment. You can change your annual commitment's renewal plan at any time before the commitment end date.
Console
You can change your renewal plan for an annual commitment as follows:
In the Google Cloud console, go to the BigQuery page.
In the navigation panel, go to the Capacity Management section.
Click the Slot commitments tab.
Find the commitment you want to edit.
Click
Actions, and then select the Edit renewal plan option.Select the new renewal plan.
bq
To change the renewal plan choice for an annual commitment, use the
bq update
command
with the
--capacity_commitment
flag
and the --renewal_plan
flag.
bq update \ --project_id=ADMIN_PROJECT_ID \ --location=LOCATION \ --renewal_plan=PLAN_TYPE \ --capacity_commitment=true \ COMMITMENT_ID
Replace the following:
ADMIN_PROJECT_ID
: the project ID of the administration project that will maintain ownership this commitmentLOCATION
: the location of the commitmentPLAN_TYPE
: the plan type, such asFLEX
,MONTHLY
, orANNUAL
.COMMITMENT_ID
: the ID of the commitmentTo get the ID, see View purchased commitments.
Convert a commitment to longer duration
You can choose to convert your commitment to a longer-duration commitment type at any time:
- You can convert your flex slots commitment to a monthly or annual commitment.
- You can convert your monthly commitment to an annual commitment.
As soon as you update your commitment, you are charged the rate associated with the new plan, and the end date resets.
To convert a commitment, use the
bq update
command
with the
--plan
flag.
bq update \ --project_id=ADMIN_PROJECT_ID \ --location=LOCATION \ --plan=PLAN_TYPE \ --renewal_plan=RENEWAL_PLAN \ --capacity_commitment=true \ COMMITMENT_ID
Replace the following:
ADMIN_PROJECT_ID
: the project IDLOCATION
: the location of the commitmentPLAN_TYPE
: the plan type, such asFLEX
,MONTHLY
, orANNUAL
.RENEWAL_PLAN
: the renewal planThis applies only if the
PLAN_TYPE
isANNUAL
. If thePLAN_TYPE
isMONTHLY
, omit this flag.COMMITMENT_ID
: the ID of the commitmentTo get the ID, see View purchased commitments.
Split a commitment
You can split your commitment into two commitments. This can be useful if you want to renew part of a commitment. For example, if you have an annual commitment of 1,000 slots, you could split off 300 slots into a new commitment, leaving 700 slots in the original commitment. You could then renew 700 slots at the annual rate, and convert 300 slots to flex slots after the end date.
When you split a commitment, the new commitment has the same plan and the same commitment end date as the original commitment.
Console
In the Google Cloud console, go to the BigQuery page.
In the navigation panel, go to the Capacity Management section.
Click the Slot commitments tab.
Select the commitment that you want to split.
Click Split.
In the Split commitment page, use the Configure split slider to select how many slots go into each split, in increments of 100 slots.
Click Split to split the commitment. The new commitment is listed in the Slot commitments tab.
bq
To split commitments, use the bq update
command.
bq update \ --project_id=ADMIN_PROJECT_ID \ --location=LOCATION \ --split \ --slots=SLOTS_TO_SPLIT \ --capacity_commitment=true \ COMMITMENT_ID
Replace the following:
ADMIN_PROJECT_ID
: the project IDLOCATION
: the location of the commitmentSLOTS_TO_SPLIT
: the number of slots to split from the original commitment into a new commitmentCOMMITMENT_ID
: the ID of the commitmentTo get the ID, see View purchased commitments.
Merge two commitments
You can merge multiple commitments into one commitment. The merging commitments
must all be of the same type (FLEX
, MONTHLY
, ANNUAL
, or THREE_YEAR
). The end
date of the combined commitment is the maximum end date of the original
commitments. If any of the commitments have an earlier end date,
they are extended to the later date and you are charged a prorated amount for
those slots.
Console
In the Google Cloud console, go to the BigQuery page.
In the navigation panel, go to the Capacity Management section.
Click the Slot commitments tab.
Select the commitments that you want to merge.
Click Merge.
In the Merge commitments page, review the details of the merge and click Merge. The new merged commitment is listed in the Slot commitments tab.
bq
To merge two commitments into one commitment, use the bq update
command:
bq update \ --project_id=ADMIN_PROJECT_ID \ --location=LOCATION \ --merge=true \ --capacity_commitment=true \ COMMITMENT1,COMMITMENT2
Replace the following:
ADMIN_PROJECT_ID
: the project IDLOCATION
: the location of the commitmentsCOMMITMENT1
: the first commitment to mergeCOMMITMENT2
: the second commitment to merge
Delete a commitment
You can delete a capacity commitment if its end date is in the past. The commitment end date is shown in the Google Cloud console. Before you delete a commitment, make sure there are enough unallocated slots. If not, you must decrease the number of slots in a reservation or remove reservations entirely.
Required permissions
To delete capacity commitments, you need the following Identity and Access Management (IAM) permission:
bigquery.capacityCommitments.delete
on the administration project that maintains ownership of the commitments.
Each of the following predefined IAM roles includes this permission:
BigQuery Admin
BigQuery Resource Admin
For more information about IAM roles in BigQuery, see Predefined roles and permissions.
Deleting a capacity commitment
Console
To delete a capacity commitment, complete the following steps:
In the Google Cloud console, go to the BigQuery page.
In the navigation panel, go to the Capacity management section.
Click the Slot commitments tab.
In the Location drop-down list, select the appropriate location.
Find the commitment you want to delete.
Expand the
Actions option.Click Delete.
Type "REMOVE" and click Proceed.
SQL
To delete a capacity commitment, use the
DROP CAPACITY
DDL statement.
In the Google Cloud console, go to the BigQuery page.
In the query editor, enter the following statement:
DROP CAPACITY `ADMIN_PROJECT_ID.region-LOCATION.COMMITMENT_ID`;
Replace the following:
ADMIN_PROJECT_ID
: the project that owns the commitmentLOCATION
: the location of the commitmentCOMMITMENT_ID
: the ID of the commitmentTo get the ID, see View purchased commitments.
Click
Run.
For more information about how to run queries, see Run an interactive query.
bq
To delete a capacity commitment, use the bq rm
command with the
--capacity_commitment
flag:
bq rm \ --project_id=ADMIN_PROJECT_ID \ --location=LOCATION \ --capacity_commitment=true \ COMMITMENT_ID
Replace the following:
ADMIN_PROJECT_ID
: the project IDLOCATION
: the location of the commitmentCOMMITMENT_ID
: the ID of the commitment you want to deleteTo get the ID, see View purchased commitments.
Troubleshooting capacity commitments
This section describes troubleshooting steps that you might find helpful if you run into problems using BigQuery Reservations.
Purchased slots are pending
Slots are subject to available capacity. When you purchase slot commitments and BigQuery allocates them, then the Status column shows a check mark. If BigQuery can't allocate the requested slots immediately, then the Status column remains pending. You might have to wait several hours for the slots to become available. If you need access to slots sooner, try the following:
- Delete the pending commitment.
- Purchase a new commitment for a smaller number of slots. Depending on capacity, the smaller commitment might become active immediately.
- Purchase the remaining slots as a separate commitment. These slots might show as pending in the Status column, but they generally become active within a few hours.
- Optional: When both commitments are available, you can merge them into a single commitment, as long as you purchased the same plan for both.
If a slot commitment fails or takes a long time to complete, consider using on-demand pricing temporarily. With this solution, you might need to run critical queries on a different project that's not assigned to any reservations, or you might need to remove the project assignment altogether.