RESERVATION_CHANGES view

TheINFORMATION_SCHEMA.RESERVATION_CHANGES view contains a near real-time listof all changes to reservations within the administration project. Each rowrepresents a change to a single reservation. For more information, seeIntroduction to reservations.

Note: The view namesINFORMATION_SCHEMA.RESERVATION_CHANGES andINFORMATION_SCHEMA.RESERVATION_CHANGES_BY_PROJECT are synonymous andcan be used interchangeably.

Required permission

To query theINFORMATION_SCHEMA.RESERVATION_CHANGES view, you needthebigquery.reservations.list Identity and Access Management (IAM) permission on theproject.Each of the following predefined IAM roles includes the requiredpermission:

BigQuery Resource Admin (roles/bigquery.resourceAdmin)
BigQuery Resource Editor (roles/bigquery.resourceEditor)
BigQuery Resource Viewer (roles/bigquery.resourceViewer)
BigQuery User (roles/bigquery.user)
BigQuery Admin (roles/bigquery.admin)

For more information about BigQuery permissions, see BigQuery IAM roles and permissions.

Schema

TheINFORMATION_SCHEMA.RESERVATION_CHANGES view has thefollowing schema:

Column name	Data type	Value
`change_timestamp`	`TIMESTAMP`	Time when the change occurred.
`project_id`	`STRING`	ID of the administration project.
`project_number`	`INTEGER`	Number of the administration project.
`reservation_name`	`STRING`	User provided reservation name.
`ignore_idle_slots`	`BOOL`	If false, any query using this reservation can use unused idle slots from other capacity commitments.
`action`	`STRING`	Type of event that occurred with the reservation. Can be`CREATE`,`UPDATE`, or`DELETE`.
`slot_capacity`	`INTEGER`	Baseline of the reservation.
`user_email`	`STRING`	Email address of the user or subject of theworkforce identity federation that made the change.`google` for changes made by Google.`NULL` if the email address is unknown.
`target_job_concurrency`	`INTEGER`	The target number of queries that can execute simultaneously, which is limited by available resources. If zero, then this value is computed automatically based on available resources.
`autoscale`	`STRUCT`	Information about the autoscale capacity of the reservation. Fields include the following: `current_slots`: the number of slots added to the reservation by autoscaling.Note: After users reduce`max_slots`, it may take a while before it can be propagated, so`current_slots` may stay in the original value and could be larger than`max_slots` for that brief period (less than one minute). `max_slots`: the maximum number of slots that could be added to the reservation by autoscaling.
`edition`	`STRING`	The edition associated with this reservation. For more information about editions, seeIntroduction to BigQuery editions.
`primary_location`	`STRING`	The current location of the reservation's primary replica. This field is only set for reservations using themanaged disaster recovery feature.
`secondary_location`	`STRING`	The current location of the reservation's secondary replica. This field is only set for reservations using themanaged disaster recovery feature.
`original_primary_location`	`STRING`	The location where the reservation was originally created.
`labels`	`RECORD`	Array of labels associated with the reservation.
`reservation_group_path`	`STRING`	The hierarchical group structure to which the reservation is linked. For example, if the group structure includes a parent group and a child group, the`reservation_group_path` field contains a list such as:`[parent group, child group]`. This field is inPreview.
`max_slots`	`INTEGER`	The maximum number of slots that this reservation can use, which includes baseline slots (`slot_capacity`), idle slots (if`ignore_idle_slots` is false), and autoscale slots. This field is specified by users for using thereservation predictability feature.
`scaling_mode`	`STRING`	The scaling mode for the reservation, which determines how the reservation scales from baseline to`max_slots`. This field is specified by users for using thereservation predictability feature.

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.

Data retention

This view contains current reservations and deleted reservations that arekept for a maximum of 41 days after which they are removedfrom the view.

Scope and syntax

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

View name	Resource scope	Region scope
[PROJECT_ID].`region-REGION`.INFORMATION_SCHEMA.RESERVATION_CHANGES[_BY_PROJECT]	Project level	`REGION`

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 use a region qualifier to queryINFORMATION_SCHEMA views. The location of the query execution must match the region of theINFORMATION_SCHEMA view.

Example

The following example gets the history of changes for a given reservation. Usethis information to see the list of changes made to a specific reservation, suchas creating or deleting the reservation.

SELECT*FROMreservation-admin-project.`region-us`.INFORMATION_SCHEMA.RESERVATION_CHANGESWHEREreservation_name="my-reservation"ORDERBYchange_timestampDESC;

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.