Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Pengantar clone tabel
Dokumen ini memberikan ringkasan tentang clone tabel di BigQuery.
Dokumen ini ditujukan bagi
pengguna yang sudah memahami BigQuery
dan tabel BigQuery.
Clone table adalah salinan ringan yang dapat ditulis dari tabel lain
(disebut tabel dasar). Anda hanya dikenai biaya untuk penyimpanan data dalam
clone tabel yang berbeda dengan tabel dasar, sehingga pada awalnya tidak ada
biaya penyimpanan untuk clone tabel. Selain model penagihan untuk penyimpanan, dan beberapa
metadata tambahan untuk tabel dasar, clone tabel mirip
dengan tabel standar. Anda dapat membuat kueri, membuat salinannya, menghapusnya, dan seterusnya.
Kasus penggunaan umum untuk clone tabel mencakup:
Membuat salinan tabel produksi yang dapat Anda gunakan untuk pengembangan dan
pengujian.
Membuat sandbox bagi pengguna untuk menghasilkan analisis dan
manipulasi data mereka sendiri, tanpa menyalin semua data produksi secara fisik.
Hanya data yang diubah yang akan ditagih.
Setelah Anda membuat clone tabel, clone tersebut akan terpisah dari tabel dasar. Setiap perubahan
yang dibuat pada tabel dasar atau clone tabel tidak akan diterapkan di tabel lain.
Jika Anda memerlukan salinan tabel yang bersifat hanya baca dan ringan, sebaiknya gunakan
snapshot tabel.
Metadata clone tabel
Clone tabel memiliki metadata yang sama dengan tabel standar, ditambah berikut ini:
Project, set data, dan nama tabel dasar clone tabel.
Waktu operasi clone tabel. Jika
perjalanan waktu digunakan untuk membuat clone tabel,
maka ini adalah stempel waktu perjalanan waktu.
Secara umum, Anda menggunakan clone tabel dengan cara yang sama seperti menggunakan
tabel standar, termasuk operasi
berikut:
Membuat kueri
Kontrol akses
Mendapatkan metadata
Partisi dan pengelompokan
Menggunakan skema
Menghapus
Namun, pembuatan clone tabel berbeda dengan pembuatan
tabel standar. Untuk mengetahui informasi selengkapnya, lihat
Membuat clone tabel.
Biaya penyimpanan
Biaya penyimpanan berlaku untuk clone tabel
tetapi BigQuery hanya mengenakan biaya untuk data dalam clone tabel
yang belum ditagihkan ke tabel lain:
Saat clone tabel dibuat, awalnya tidak ada biaya penyimpanan untuk
clone tabel tersebut.
Jika data ditambahkan atau diubah dalam clone tabel, Anda akan dikenai
biaya untuk penyimpanan data yang ditambahkan atau diperbarui.
Jika data dihapus dalam clone tabel, Anda tidak akan dikenai biaya untuk penyimpanan data yang dihapus.
Jika data diubah atau dihapus dalam tabel dasar yang juga ada dalam clone
tabel, Anda akan dikenai biaya untuk penyimpanan clone tabel dari data yang
diubah atau dihapus. Jika ada beberapa clone yang berisi data yang diubah atau dihapus,
Anda hanya dikenai biaya untuk penyimpanan yang digunakan oleh clone terlama.
Jika data ditambahkan ke tabel dasar setelah clone tabel
dibuat, Anda tidak akan dikenai biaya untuk penyimpanan data tersebut dalam clone tabel,
tetapi Anda akan dikenai biaya untuk penyimpanan tersebut di tabel dasar.
Perbedaan antara biaya penyimpanan clone tabel dan tabel dasar ditampilkan dalam
gambar berikut:
Anda dapat meng-clone tabel antar-set data dalam project yang sama, dan di antara
set data dalam project yang berbeda. Namun, set data tujuan untuk clone tabel harus berada di region yang sama dan dalam organisasi yang sama dengan tabel yang sedang di-clone. Misalnya, Anda tidak dapat meng-clone tabel dari set data yang berbasis di Uni Eropa ke set data yang berbasis di AS.
Anda tidak dapat membuat clone data tabel karena data tabel tersebut jauh
lebih lama dari durasi periode perjalanan waktu untuk set data tabel tersebut.
Jika Anda meng-clone tabel yang memiliki data dalam perjalanan waktu, data dalam perjalanan waktu tidak disertakan dalam clone tabel.
Clone tabel tidak dapat dibedakan dari tabel standar di panel Explorer. Namun, Anda dapat mengetahui clone tabel dari tabel standar
dengan
melihat detail tabel.
Detail clone tabel memiliki bagian Info Tabel Dasar yang tidak disertakan
pada tabel standar.
Anda tidak dapat menggunakan operasi clone untuk menambahkan data ke tabel yang ada. Misalnya, Anda tidak dapat menggunakan setelan flag --append_table=true dan --clone=true dalam perintah bq cp yang sama. Untuk menambahkan data saat menduplikasi tabel, gunakan operasi penyalinan.
Saat Anda membuat clone tabel, namanya harus mematuhi aturan penamaan yang sama seperti saat Anda membuat tabel.
Pembuatan clone tabel tunduk pada batas BigQuery pada tugas penyalinan.
Waktu yang diperlukan BigQuery untuk membuat clone tabel dapat bervariasi secara signifikan di berbagai operasi karena penyimpanan yang mendasarinya dikelola secara dinamis.
Kuota dan batas
Clone tabel memiliki kuota dan batas yang sama dengan tabel standar. Untuk mengetahui informasi lebih lanjut, lihat kuota dan batas tabel. Clone tabel juga memiliki batas clone tabel yang berlaku.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-17 UTC."],[[["\u003cp\u003eTable clones are writable, lightweight copies of a base table, incurring storage costs only for data that differs from the base table.\u003c/p\u003e\n"],["\u003cp\u003eCommon uses for table clones include creating development/testing environments and sandboxes for user analytics without duplicating all production data.\u003c/p\u003e\n"],["\u003cp\u003eTable clones are independent of their base tables, meaning changes to one are not reflected in the other.\u003c/p\u003e\n"],["\u003cp\u003eTable clones have similar functionality to standard tables, allowing for querying, access control, and deletion, among other operations.\u003c/p\u003e\n"],["\u003cp\u003eStorage 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.\u003c/p\u003e\n"]]],[],null,["# Introduction to table clones\n============================\n\nThis document gives an overview of table clones in BigQuery.\nIt is intended for\nusers who are familiar with [BigQuery](/bigquery/docs)\nand BigQuery [tables](/bigquery/docs/tables-intro).\n\nA *table clone* is a lightweight, writable copy of another table\n(called the *base table*). You are only charged for storage of data in the\ntable clone that differs from the base table, so initially there is no storage\ncost for a table clone. Other than the billing model for storage, and some\nadditional metadata for the base table, a table clone is similar to a\nstandard table---you can query it, make a copy of it, delete it, and so on.\n\nCommon use cases for table clones include the following:\n\n- Creating copies of production tables that you can use for development and testing.\n- 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.\n\nAfter you create a table clone, it is independent of the base table. Any changes\nmade to the base table or table clone aren't reflected in the other.\n\nIf you need read-only, lightweight copies of your tables, consider using\n[table snapshots](/bigquery/docs/table-snapshots-intro).\n\nTable clone metadata\n--------------------\n\nA table clone has the same metadata as a standard table, plus the following:\n\n- The project, dataset, and name of the table clone's base table.\n- The time of the table clone operation. If [time travel](/bigquery/docs/time-travel) was used to create the table clone, then this is the time travel timestamp.\n\nFor more information, see\n[INFORMATION_SCHEMA.TABLES](/bigquery/docs/information-schema-tables).\n\nTable clone operations\n----------------------\n\nIn general, you use table clones in the same way as you use\n[standard tables](/bigquery/docs/managing-tables), including the following\noperations:\n\n- Querying\n- Access control\n- Getting metadata\n- Partitioning and clustering\n- Working with schemas\n- Deleting\n\nHowever, the creation of a table clone is different from the creation of a\nstandard table. For more information, see\n[Create table clones](/bigquery/docs/table-clones-create).\n\nStorage costs\n-------------\n\n[Storage costs](/bigquery/pricing#storage) apply for table clones,\nbut BigQuery only charges for the data in a table\nclone that is not already charged to another table:\n\n- When a table clone is created, there is initially no storage cost for the\n table clone.\n\n- If data is added or changed in a table clone, then you are charged for the\n storage of the added or updated data.\n\n- If data is deleted in a table clone, then you are not charged for the storage\n of the deleted data.\n\n- If data is changed or deleted in the base table that also exists in a table\n clone, then you are charged for the table clone storage of the changed or\n deleted data. If there are multiple clones that contain the changed or\n deleted data, you are only charged for the storage used by the oldest clone.\n\n- If data is added to the base table after the table clone was\n created, then you aren't charged for storage of that data in the table clone,\n but you are charged for it in the base table,\n\nThe difference between base table and table clone storage charges is shown in\nthe following image:\n\n| **Note:**\n| - 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.\n| - 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](/bigquery/docs/creating-clustered-tables#modifying-cluster-spec), 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.\n| - 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.\n\nFor more information, see\n[BigQuery storage pricing](/bigquery/pricing#storage).\n\nLimitations\n-----------\n\n- 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](/bigquery/docs/locations), and under the same [organization](/resource-manager/docs/creating-managing-organization), as the table being cloned. For example, you cannot clone a table from an EU-based dataset into a US-based dataset.\n- You can't create a clone of a table's data as it was further back than the duration of the [time travel](/bigquery/docs/time-travel) window for the table's dataset.\n- You can't create a clone of a [view](/bigquery/docs/views-intro) or a [materialized view](/bigquery/docs/materialized-views-intro).\n- You can't create a clone of an [external table](/bigquery/docs/external-tables).\n- If you clone a table that has data in write-optimized storage (the [streaming buffer for recently streamed rows](/bigquery/docs/streaming-data-into-bigquery#dataavailability)), the data in the write-optimized storage is not included in the table clone.\n- If you clone a table that has data in [time travel](/bigquery/docs/time-travel), the data in time travel is not included in the table clone.\n- 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](/bigquery/docs/tables#get_table_information_using_information_schema). Table clone details have a **Base Table Info** section that standard tables don't.\n- 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`](/bigquery/docs/reference/bq-cli-reference#bq_cp) command. To append data when duplicating a table, use a copy operation instead.\n- When you create a table clone, its name must adhere to the same [naming rules](/bigquery/docs/tables#table_naming) as when you create a table.\n- Table clone creation is subject to BigQuery [limits](/bigquery/quotas#copy_jobs) on copy jobs.\n- The time that BigQuery takes to create table clones might vary significantly across different runs because the underlying storage is managed dynamically.\n\nQuotas and limits\n-----------------\n\nTable clones are subject to the same quotas and limits as standard tables. For\nmore information, see\n[table quotas and limits](/bigquery/quotas#table_limits). They also have\n[table clone limits](/bigquery/quotas#table_clones) that apply.\n\nWhat's next\n-----------\n\n- [Create a table clone](/bigquery/docs/table-clones-create)."]]
