RetroSearch Browse

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://developers.google.com/bigquery/docs/table-clones-intro below:

Introduction to table clones | BigQuery

Stay organized with collections Save and categorize content based on your preferences.

Introduction to table clones

This document gives an overview of table clones in BigQuery. It is intended for users who are familiar with BigQuery and BigQuery tables.

A table clone is a lightweight, writable copy of another table (called the base table). You are only charged for storage of data in the table clone that differs from the base table, so initially there is no storage cost for a table clone. Other than the billing model for storage, and some additional metadata for the base table, a table clone is similar to a standard table—you can query it, make a copy of it, delete it, and so on.

Common use cases for table clones include the following:

Creating copies of production tables that you can use for development and testing.
Creating sandboxes for users to generate their own analytics and data manipulations, without physically copying all of the production data. Only the changed data is billed.

After you create a table clone, it is independent of the base table. Any changes made to the base table or table clone aren't reflected in the other.

If you need read-only, lightweight copies of your tables, consider using table snapshots.

A table clone has the same metadata as a standard table, plus the following:

The project, dataset, and name of the table clone's base table.
The time of the table clone operation. If time travel was used to create the table clone, then this is the time travel timestamp.

For more information, see INFORMATION_SCHEMA.TABLES.

Table clone operations

In general, you use table clones in the same way as you use standard tables, including the following operations:

Querying
Access control
Getting metadata
Partitioning and clustering
Working with schemas
Deleting

However, the creation of a table clone is different from the creation of a standard table. For more information, see Create table clones.

Storage costs

Storage costs apply for table clones, but BigQuery only charges for the data in a table clone that is not already charged to another table:

When a table clone is created, there is initially no storage cost for the table clone.
If data is added or changed in a table clone, then you are charged for the storage of the added or updated data.
If data is deleted in a table clone, then you are not charged for the storage of the deleted data.
If data is changed or deleted in the base table that also exists in a table clone, then you are charged for the table clone storage of the changed or deleted data. If there are multiple clones that contain the changed or deleted data, you are only charged for the storage used by the oldest clone.
If data is added to the base table after the table clone was created, then you aren't charged for storage of that data in the table clone, but you are charged for it in the base table,

The difference between base table and table clone storage charges is shown in the following image:

Note:Because BigQuery storage is column-based, small changes to the data in a base table can result in large increases in storage cost for a clone of the table. Some changes to a base table can result in you being charged the full storage amount for a table clone of the table. For example, if you modify a base table with clustering, that can lead to automatic re-clustering. Because re-clustering can rewrite the base table's storage blocks, the base table's storage is no longer the same as the storage of its clones. This causes the oldest of the base table's clones to be charged the full storage amount of the modified partition. Partitions can help reduce storage costs for table clones. In general, BigQuery only makes a copy of modified data within a partition, instead of the entire table clone.

For more information, see BigQuery storage pricing.

Limitations

You can clone a table between datasets in the same project, and between datasets in different projects. However, the destination dataset for the table clone must be in the same region, and under the same organization, as the table being cloned. For example, you cannot clone a table from an EU-based dataset into a US-based dataset.
You can't create a clone of a table's data as it was further back than the duration of the time travel window for the table's dataset.
You can't create a clone of a view or a materialized view.
You can't create a clone of an external table.
If you clone a table that has data in write-optimized storage (the streaming buffer for recently streamed rows), the data in the write-optimized storage is not included in the table clone.
If you clone a table that has data in time travel, the data in time travel is not included in the table clone.
Table clones can't be distinguished from standard tables in the Explorer pane. However, you can tell a table clone from a standard table by looking at the table details. Table clone details have a Base Table Info section that standard tables don't.
You can't use a clone operation to append data to an existing table. For example, you can't use the flag settings --append_table=true and --clone=true in the same bq cp command. To append data when duplicating a table, use a copy operation instead.
When you create a table clone, its name must adhere to the same naming rules as when you create a table.
Table clone creation is subject to BigQuery limits on copy jobs.
The time that BigQuery takes to create table clones might vary significantly across different runs because the underlying storage is managed dynamically.

Quotas and limits

Table clones are subject to the same quotas and limits as standard tables. For more information, see table quotas and limits. They also have table clone limits that apply.

What's next

Create a table clone.

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

Last updated 2025-08-07 UTC.

[[["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-08-07 UTC."],[[["Table clones are writable, lightweight copies of a base table, incurring storage costs only for data that differs from the base table."],["Common uses for table clones include creating development/testing environments and sandboxes for user analytics without duplicating all production data."],["Table clones are independent of their base tables, meaning changes to one are not reflected in the other."],["Table clones have similar functionality to standard tables, allowing for querying, access control, and deletion, among other operations."],["Storage costs for table clones are incurred when data is added, updated, or if data is changed or deleted in the base table that also exist in the clone."]]],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4