Stay organized with collectionsSave and categorize content based on your preferences.
RESERVATION_CHANGES view
TheINFORMATION_SCHEMA.RESERVATION_CHANGESview contains a near real-time list
of all changes to reservations within the administration project. Each row
represents a change to a single reservation. For more information, seeIntroduction to reservations.
Required permission
To query theINFORMATION_SCHEMA.RESERVATION_CHANGESview, you need
thebigquery.reservations.listIdentity and Access Management (IAM) permission on the
project.
Each of the following predefined IAM roles includes the required
permission:
TheINFORMATION_SCHEMA.RESERVATION_CHANGESview has the
following 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 beCREATE,UPDATE, orDELETE.
slot_capacity
INTEGER
Baseline of the reservation.
user_email
STRING
Email address of the user or subject of theworkforce identity
federationthat made the change.googlefor changes
made by Google.NULLif 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.
max_slots: the maximum number of slots that could be added to the reservation by autoscaling.
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.
max_slots
INTEGER
The maximum number of slots that this reservation can use, which includes
baseline slots (slot_capacity), idle slots (ifignore_idle_slotsis 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 tomax_slots. This field is specified by users for using thereservation predictability feature.
Data retention
This view contains current reservations and deleted reservations that are
kept for a maximum of 41 days after which they are removed
from 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 all
regions. The following table explains the region scope for this view:
The following example gets the history of changes for a given reservation. Use
this information to see the list of changes made to a specific reservation, such
as creating or deleting the reservation.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[[["\u003cp\u003eThe \u003ccode\u003eINFORMATION_SCHEMA.RESERVATION_CHANGES\u003c/code\u003e view provides a real-time log of all changes made to reservations within the administration project, with each row representing a single change event.\u003c/p\u003e\n"],["\u003cp\u003eQuerying this view requires the \u003ccode\u003ebigquery.reservations.list\u003c/code\u003e IAM permission, which is included in several predefined roles like \u003ccode\u003eroles/bigquery.resourceAdmin\u003c/code\u003e and \u003ccode\u003eroles/bigquery.user\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eEach entry in the view includes details like the \u003ccode\u003echange_timestamp\u003c/code\u003e, \u003ccode\u003eproject_id\u003c/code\u003e, \u003ccode\u003ereservation_name\u003c/code\u003e, \u003ccode\u003eaction\u003c/code\u003e (CREATE, UPDATE, DELETE), and other information about the change.\u003c/p\u003e\n"],["\u003cp\u003eThe view retains data on current and deleted reservations for up to 41 days before they are removed.\u003c/p\u003e\n"],["\u003cp\u003eQueries to this view need to specify a region using a region qualifier, and the query execution location must match the region of the view.\u003c/p\u003e\n"]]],[],null,["# RESERVATION_CHANGES view\n========================\n\nThe `INFORMATION_SCHEMA.RESERVATION_CHANGES` view contains a near real-time list\nof all changes to reservations within the administration project. Each row\nrepresents a change to a single reservation. For more information, see\n[Introduction to reservations](/bigquery/docs/reservations-intro).\n\nRequired permission\n-------------------\n\nTo query the `INFORMATION_SCHEMA.RESERVATION_CHANGES` view, you need\nthe `bigquery.reservations.list` Identity and Access Management (IAM) permission on the\nproject.\nEach of the following predefined IAM roles includes the required\npermission:\n\n- BigQuery Resource Admin (`roles/bigquery.resourceAdmin`)\n- BigQuery Resource Editor (`roles/bigquery.resourceEditor`)\n- BigQuery Resource Viewer (`roles/bigquery.resourceViewer`)\n- BigQuery User (`roles/bigquery.user`)\n- BigQuery Admin (`roles/bigquery.admin`)\n\nFor more information about BigQuery permissions, see\n[BigQuery IAM roles and permissions](/bigquery/docs/access-control).\n\nSchema\n------\n\nThe `INFORMATION_SCHEMA.RESERVATION_CHANGES` view has the\nfollowing schema:\n\nData retention\n--------------\n\nThis view contains current reservations and deleted reservations that are\nkept for a maximum of 41 days after which they are removed\nfrom the view.\n\nScope and syntax\n----------------\n\nQueries against this view must include a [region qualifier](/bigquery/docs/information-schema-intro#syntax).\nIf you do not specify a regional qualifier, metadata is retrieved from all\nregions. The following table explains the region scope for this view:\n\nReplace the following:\n\n- Optional: \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: the ID of your Google Cloud project. If not specified, the default project is used.\n- \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e: any [dataset region name](/bigquery/docs/locations). For example, ```region-us```.\n\n \u003cbr /\u003e\n\n \u003cbr /\u003e\n\n | **Note:** You must use [a region qualifier](/bigquery/docs/information-schema-intro#region_qualifier) to query `INFORMATION_SCHEMA` views. The location of the query execution must match the region of the `INFORMATION_SCHEMA` view.\n\n\u003cbr /\u003e\n\nExample\n-------\n\nThe following example gets the history of changes for a given reservation. Use\nthis information to see the list of changes made to a specific reservation, such\nas creating or deleting the reservation. \n\n```googlesql\nSELECT\n *\nFROM\n reservation-admin-project.`region-us`.\n INFORMATION_SCHEMA.RESERVATION_CHANGES\nWHERE\n reservation_name = \"\u003cvar translate=\"no\"\u003emy-reservation\u003c/var\u003e\"\nORDER BY\n change_timestamp DESC;\n```"]]
