TABLE_STORAGE view

The INFORMATION_SCHEMA.TABLE_STORAGE view provides a current snapshot of storage usage for tables and materialized views. When you query the INFORMATION_SCHEMA.TABLE_STORAGE view, the query results contain one row for each table or materialized view for the current project. The data in this table is not kept in real time, and might be delayed by a few seconds to a few minutes.

The table storage views give you a convenient way to observe your current storage consumption, and in addition provide details on whether your storage uses logical uncompressed bytes, physical compressed bytes, or time travel bytes. This information can help you with tasks like planning for future growth and understanding the update patterns for tables.

Data included in the `*_BYTES` columns

The *_BYTES columns in the table storage views include information about your use of storage bytes. This information is determined by looking at your storage usage for materialized views and the following types of tables:

Permanent tables created through any of the methods described in Create and use tables.
Temporary tables generated in sessions and multi-statement queries ("scripts").

Data stored in the query results cache is not billed to you and so is not included in the *_BYTES column values.

Storage usage by clones and snapshots is billed, but information about clones and snapshots isn't included in the table storage views.

Forecast storage billing

In order to forecast the monthly storage billing for a dataset, you can use either the logical or physical *_BYTES columns in this view, depending on the dataset storage billing model used by the dataset. Please note that this is only a rough forecast, and the precise billing amounts are calculated based on the usage by BigQuery storage billing infrastructure and visible in Cloud Billing.

For datasets that use a logical billing model, you can forecast your monthly storage costs as follows:

((ACTIVE_LOGICAL_BYTES value / POW(1024, 3)) * active logical bytes pricing) + ((LONG_TERM_LOGICAL_BYTES value / POW(1024, 3)) * long-term logical bytes pricing)

The ACTIVE_LOGICAL_BYTES value for a table reflects the active bytes currently used by that table.

For datasets that use a physical billing model, you can forecast your storage costs as follows:

((ACTIVE_PHYSICAL_BYTES value / POW(1024, 3)) * active physical bytes pricing) + ((LONG_TERM_PHYSICAL_BYTES value / POW(1024, 3)) * long-term physical bytes pricing)

The ACTIVE_PHYSICAL_BYTES value for a table reflects the active bytes currently used by that table plus the bytes used for time travel for that table.

To see the active bytes of the table alone, subtract the TIME_TRAVEL_PHYSICAL_BYTES value from the ACTIVE_PHYSICAL_BYTES value.

For more information, see Storage pricing.

Required roles

To get the permissions that you need to query the INFORMATION_SCHEMA.TABLE_STORAGE view, ask your administrator to grant you the BigQuery Metadata Viewer (roles/bigquery.metadataViewer) IAM role on the project. For more information about granting roles, see Manage access.

This predefined role contains the permissions required to query the INFORMATION_SCHEMA.TABLE_STORAGE view. To see the exact permissions that are required, expand the Required permissions section:

Required permissions

The following permissions are required to query the INFORMATION_SCHEMA.TABLE_STORAGE view:

bigquery.tables.get
bigquery.tables.list

You might also be able to get these permissions with custom roles or other predefined roles.

Schema

The INFORMATION_SCHEMA.TABLE_STORAGE view has the following schema:

Column name	Data type	Value
`PROJECT_ID`	`STRING`	The project ID of the project that contains the dataset
`PROJECT_NUMBER`	`INT64`	The project number of the project that contains the dataset
`TABLE_SCHEMA`	`STRING`	The name of the dataset that contains the table or materialized view, also referred to as the `datasetId`
`TABLE_NAME`	`STRING`	The name of the table or materialized view, also referred to as the `tableId`
`CREATION_TIME`	`TIMESTAMP`	The table's creation time
`DELETED`	`BOOLEAN`	Indicates whether or not the table is deleted
`STORAGE_LAST_MODIFIED_TIME`	`TIMESTAMP`	The most recent time that data was written to the table.
`TOTAL_ROWS`	`INT64`	The total number of rows in the table or materialized view
`TOTAL_PARTITIONS`	`INT64`	The number of partitions present in the table or materialized view. Unpartitioned tables return 0.
`TOTAL_LOGICAL_BYTES`	`INT64`	Total number of logical (uncompressed) bytes in the table or materialized view
`ACTIVE_LOGICAL_BYTES`	`INT64`	Number of logical (uncompressed) bytes that are less than 90 days old
`LONG_TERM_LOGICAL_BYTES`	`INT64`	Number of logical (uncompressed) bytes that are more than 90 days old
`TOTAL_PHYSICAL_BYTES`	`INT64`	Total number of physical (compressed) bytes used for storage, including active, long term, and time travel (deleted or changed data) bytes
`ACTIVE_PHYSICAL_BYTES`	`INT64`	Number of physical (compressed) bytes less than 90 days old, including time travel (deleted or changed data) bytes
`LONG_TERM_PHYSICAL_BYTES`	`INT64`	Number of physical (compressed) bytes more than 90 days old
`TIME_TRAVEL_PHYSICAL_BYTES`	`INT64`	Number of physical (compressed) bytes used by time travel storage (deleted or changed data)
`TABLE_TYPE`	`STRING`	The type of table. For example, `EXTERNAL` or `BASE TABLE`

Scope and syntax

Queries against this view must include a region qualifier. The following table explains the region scope for this view:

View name	Resource scope	Region scope
[`PROJECT_ID`.]`region-REGION`.INFORMATION_SCHEMA.TABLE_STORAGE[_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: any dataset region name. For example, region-us.

SELECT
  CONCAT(v1.table_catalog, ":", v1.table_schema, ".", v1.table_name) AS unmodified_table_name,
FROM
  `region-REGION`.INFORMATION_SCHEMA.TABLES v1
LEFT JOIN `region-REGION`.INFORMATION_SCHEMA.TABLE_STORAGE v2 ON v1.table_name = v2.table_name
WHERE v2.table_name IS NULL;

The following example shows how to return storage information for tables in a specified project:

SELECT * FROM `myProject`.`region-REGION`.INFORMATION_SCHEMA.TABLE_STORAGE;

The following example shows how to return storage information for tables in a specified region:

SELECT * FROM `region-REGION`.INFORMATION_SCHEMA.TABLE_STORAGE_BY_PROJECT;

Examples

Example 1:

The following example shows you the total logical bytes billed for the current project.

SELECT
  SUM(total_logical_bytes) AS total_logical_bytes
FROM
  `region-REGION`.INFORMATION_SCHEMA.TABLE_STORAGE;

The result is similar to the following:

+---------------------+
| total_logical_bytes |
+---------------------+
| 971329178274633     |
+---------------------+

Example 2:

The following example shows you how to calculate the price difference per dataset. This example assumes that usage was constant over the last month from the moment the query was run. Your actual bill might vary somewhat from the calculations returned by this query, because storage usage by clones and snapshots is billed, but is currently not included in the *_BYTES columns of the table storage views.

The prices used in the pricing variables for this query are for the us-central1 region. If you want to run this query for a different region, update the pricing variables appropriately. See Storage pricing for pricing information.

Open the BigQuery page in the Google Cloud console.

Go to the BigQuery page
Enter the following GoogleSQL query in the Query editor box. INFORMATION_SCHEMA requires GoogleSQL syntax. GoogleSQL is the default syntax in the Google Cloud console.
```
DECLARE active_logical_gib_price FLOAT64 DEFAULT 0.02;
DECLARE long_term_logical_gib_price FLOAT64 DEFAULT 0.01;
```