전송 구성에는 위치도 포함되어 있습니다. 전송을 설정할 때 대상 데이터 세트가 없으면 전송을 구성하기 전에 BigQuery에서 만들어야 합니다. 대상 데이터 세트와 동일한 프로젝트에서 전송 구성을 만듭니다. 전송 구성 위치는 대상 데이터 세트에 지정한 위치와 동일한 위치로 자동으로 설정됩니다. BigQuery Data Transfer Service는 대상 BigQuery 데이터 세트와 동일한 위치에서 데이터를 처리하고 스테이징합니다.
소스 데이터 위치
BigQuery로 전송하려는 소스 데이터에도 리전이 있을 수 있습니다. 경우에 따라 소스 데이터가 저장되는 리전과 BigQuery의 대상 데이터 세트의 위치는 관련성이 없습니다. 다른 유형의 전송에서는 데이터 세트와 소스 데이터가 같은 리전에 있어야 합니다.
코로케이션이 필요한 전송의 경우 소스 데이터의 리전과 다르거나 호환되지 않는 리전의 대상 데이터 세트로 전송을 설정하면 구성 오류가 발생할 수 있습니다.
전송을 위한 위치 고려 사항
코로케이션 불필요
BigQuery Data Transfer Service에서 수행하는 다음 유형의 전송은 위치에 따라 다르므로 BigQuery 데이터 세트의 위치는 관련이 없습니다.
BigQuery 데이터 세트가 멀티 리전에 있으면 전송 중인 데이터가 포함된 Cloud Storage 버킷은 동일한 멀티 리전이나 멀티 리전 내에 포함된 위치에 있어야 합니다. 예를 들어 BigQuery 데이터 세트가 `EU` 멀티 리전에 있으면 Cloud Storage 버킷은 EU 내에 있는 `europe-west1` 벨기에 리전에 있을 수 있습니다.
데이터 세트가 한 리전에 있으면 Cloud Storage 버킷은 같은 리전에 있어야 합니다. 예를 들어 데이터 세트가 `asia-northeast1` 도쿄 리전에 있으면 Cloud Storage 버킷은 `ASIA` 멀티 리전에 있을 수 없습니다.
데이터 웨어하우스 이전
Teradata에서 데이터 웨어하우스를 마이그레이션하려면 전송 프로세스 중에 Cloud Storage 버킷이 필요합니다. Cloud Storage 버킷은 BigQuery 대상 데이터 세트와 같은 위치에 배치되어야 합니다.
Redshift 데이터 웨어하우스 마이그레이션에는 코로케이션 Cloud Storage 버킷이 필요하지 않습니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2024-12-22(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."]]
