Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Lokasi dan transfer data
Halaman ini menjelaskan konsep lokasi konfigurasi
transfer dan lokasi data sumber, serta menjelaskan cara lokasi
dan transfer berinteraksi.
Untuk mengetahui informasi selengkapnya tentang lokasi BigQuery secara lebih umum, lihat Lokasi set data.
Konsep utama
Lokasi transfer
Konfigurasi transfer juga memiliki lokasi. Saat menyiapkan transfer, jika
set data tujuan tidak ada, Anda harus membuatnya di BigQuery
sebelum mengonfigurasi transfer. Buat konfigurasi transfer dalam project
yang sama dengan set data tujuan. Lokasi konfigurasi transfer
otomatis ditetapkan ke lokasi yang sama dengan yang Anda tentukan untuk set data
tujuan. BigQuery Data Transfer Service memproses dan menata data di lokasi yang sama
dengan set data BigQuery tujuan.
Lokasi data sumber
Data sumber yang ingin Anda transfer ke BigQuery mungkin juga memiliki region. Dalam
beberapa kasus, region tempat data sumber disimpan dan lokasi
set data tujuan di BigQuery tidak relevan. Dalam jenis transfer
lainnya, set data dan data sumber harus ditempatkan di
region yang sama.
Untuk transfer yang memerlukan kolokasi, menyiapkan transfer ke set data
tujuan di region yang berbeda dari, atau tidak kompatibel dengan, region data sumber
Anda dapat mengakibatkan error konfigurasi.
Pertimbangan lokasi untuk transfer
Kolokasi tidak diperlukan
Jenis transfer yang dilakukan oleh BigQuery Data Transfer Service berikut tidak memiliki
persyaratan lokasi set data BigQuery:
Transfer dari Cloud Storage ke BigQuery mengharuskan bucket Cloud Storage digabungkan dengan
set data tujuan BigQuery.
Tempatkan bucket Cloud Storage Anda untuk mentransfer data.
Jika set data BigQuery Anda berada di multi-region, bucket Cloud Storage
yang berisi data yang ditransfer harus berada di multi-region yang sama atau di lokasi
yang terdapat dalam multi-region. Misalnya, jika set data BigQuery Anda berada di multi-region EU, bucket Cloud Storage dapat berada di region Belgia europe-west1, yang berada di Uni Eropa.
Jika set data Anda berada di satu region, bucket Cloud Storage Anda harus berada di region yang sama. Misalnya, jika set data Anda berada di region Tokyo asia-northeast1, bucket Cloud Storage Anda tidak boleh berada di multi-region ASIA.
Migrasi data warehouse
Migrasi data warehouse dari
Teradata memerlukan
bucket Cloud Storage sebagai bagian dari proses transfer. Bucket Cloud Storage
harus ditempatkan bersama dengan set data tujuan BigQuery.
Migrasi data warehouse Redshift tidak memerlukan bucket Cloud Storage
yang ditempatkan bersama.
[[["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\u003eTransfer configurations are located in the same region as their destination BigQuery dataset, and the BigQuery Data Transfer Service processes data in this same location.\u003c/p\u003e\n"],["\u003cp\u003eSource data for transfers may or may not need to be colocated with the destination BigQuery dataset, depending on the type of transfer.\u003c/p\u003e\n"],["\u003cp\u003eTransfers from Google products and services, as well as external sources like Amazon S3 and third-party providers, do not require colocation.\u003c/p\u003e\n"],["\u003cp\u003eCloud Storage transfers to BigQuery mandate that the Cloud Storage bucket is colocated within the same multi-region or single region as the destination BigQuery dataset.\u003c/p\u003e\n"],["\u003cp\u003eData Warehouse migrations, such as Teradata, require the use of a Cloud Storage bucket, and the Cloud Storage bucket must be colocated with the BigQuery destination dataset.\u003c/p\u003e\n"]]],[],null,["# Data location and transfers\n===========================\n\nThis page explains the concepts of transfer configuration\nlocation and source data location, and also describes how locations\nand transfers interact.\n\nFor more information about BigQuery locations more generally, see\n[Dataset locations](/bigquery/docs/locations).\n\n\nKey concepts\n------------\n\n### Transfer location\n\nTransfer configurations also have locations. When you set up a transfer, if the\ndestination dataset does not exist, you will need to create it in BigQuery\nbefore configuring the transfer. Create the transfer configuration in the same\nproject as the destination dataset. The location of the transfer configuration is\nautomatically set to the same location that you specified for the destination\ndataset. The BigQuery Data Transfer Service processes and stages data in the same location\nas the destination BigQuery dataset.\n\n### Source data location\n\nThe source data you wish to transfer to BigQuery may also have a region. In\nsome cases, the region where your source data is stored and the location of\nthe destination dataset in BigQuery are irrelevant. In other kinds of\ntransfers, the dataset and the source data *must* be colocated in the\nsame region.\n\nFor transfers that require colocation, setting up a transfer to a destination\ndataset in a region that is different from, or not compatible with, your source\ndata's region could result in configuration errors.\n\nLocation considerations for transfers\n-------------------------------------\n\n### Colocation not necessary\n\nThe following types of transfers made by the BigQuery Data Transfer Service don't have any\nBigQuery dataset location requirements:\n\n- Reports from Google products and services\n - [Campaign Manager transfers](/bigquery/docs/doubleclick-campaign-transfer)\n - [Google Ad Manager transfers](/bigquery/docs/doubleclick-publisher-transfer)\n - [Google Ads transfers](/bigquery/docs/google-ads-transfer)\n - [Google Merchant Center transfers](/bigquery/docs/merchant-center-transfer)\n - [Google Play transfers](/bigquery/docs/play-transfer)\n - [Search Ads 360 transfers](/bigquery/docs/search-ads-transfer)\n - [YouTube Channel transfers](/bigquery/docs/youtube-channel-transfer)\n - [YouTube Content Owner transfers](/bigquery/docs/youtube-content-owner-transfer)\n- Transfers from external sources\n - [Amazon S3 transfers](/bigquery/docs/s3-transfer-intro)\n - [Third-party transfers](/bigquery/docs/third-party-transfer)\n\n### Colocation required\n\n#### Cloud Storage\n\n[Transfers from Cloud Storage](/bigquery/docs/cloud-storage-transfer-overview)\nto BigQuery require that the Cloud Storage bucket be colocated with the\nBigQuery destination dataset.\n\nColocate your Cloud Storage buckets for transferring data.\n\n\n- If your BigQuery dataset is in a multi-region, the Cloud Storage bucket containing the data you're transferring must be in the same multi-region or in a location that is contained within the multi-region. For example, if your BigQuery dataset is in the `EU` multi-region, the Cloud Storage bucket can be located in the `europe-west1` Belgium region, which is within the EU.\n- If your dataset is in a single region, your Cloud Storage bucket must be in the same region. For example, if your dataset is in the `asia-northeast1` Tokyo region, your Cloud Storage bucket cannot be in the `ASIA` multi-region.\n\n#### Data warehouse migrations\n\nData warehouse migrations from\n[Teradata](/bigquery/docs/migration/teradata-overview) require a\nCloud Storage bucket as part of the transfer process. The Cloud Storage bucket\nmust be colocated with the BigQuery destination dataset.\n\nRedshift data warehouse migrations do not require a colocated Cloud Storage\nbucket.\n| **Key Point:** You can copy a dataset or manually move it to another region. See [Managing datasets](/bigquery/docs/managing-datasets) for details. For more information about using Cloud Storage to store and move large datasets, see [Using Cloud Storage with big data](/storage/docs/working-with-big-data).\n\nWhat's next\n-----------\n\n- View [all the Google Cloud services available in locations worldwide](/about/locations#region).\n- [Explore additional location-based concepts](/docs/geography-and-regions), such as zones, that apply to other Google Cloud services."]]
