이 문서에서는 BigQuery의 저장소 개념을 설명합니다. 저장소를 사용하여 BigQuery에서 사용하는 파일의 버전 관리를 실행할 수 있습니다. BigQuery는 Git을 사용하여 변경사항을 기록하고 파일 버전을 관리합니다.
각 BigQuery 저장소는 Git 저장소를 나타냅니다. BigQuery의 내장 Git 기능을 사용하거나 서드 파티 Git 저장소에 연결할 수 있습니다. 각 저장소 내에서 하나 이상의 작업공간을 만들어 저장소에 저장된 코드를 수정할 수 있습니다.
BigQuery 페이지의 탐색기 창에 있는 저장소 폴더에 저장소가 알파벳순으로 표시됩니다.
서드 파티 저장소
원하는 경우 BigQuery 저장소를 서드 파티 Git 저장소에 연결할 수 있습니다. 이 경우 BigQuery 대신 서드 파티 저장소에 저장소 코드가 저장됩니다. BigQuery는 서드 파티 저장소와 상호작용하여 BigQuery 작업공간에서 콘텐츠를 수정하고 실행할 수 있습니다. 선택한 저장소 유형에 따라 SSH 또는 HTTPS를 사용하여 서드 파티 저장소에 연결할 수 있습니다.
다음 표에는 지원되는 Git 제공업체와 해당 저장소에 사용할 수 있는 연결 방법이 나와 있습니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[[["\u003cp\u003eBigQuery repositories allow for version control of files used within BigQuery, utilizing Git for managing changes and file versions.\u003c/p\u003e\n"],["\u003cp\u003eRepositories can either use BigQuery's built-in Git capabilities or connect to third-party Git repositories like Microsoft Azure DevOps Services, Bitbucket, GitHub, and GitLab via SSH or HTTPS.\u003c/p\u003e\n"],["\u003cp\u003eBigQuery repositories are displayed alphabetically in the \u003cstrong\u003eRepositories\u003c/strong\u003e folder within the \u003cstrong\u003eExplorer\u003c/strong\u003e pane, and each can contain multiple workspaces for editing code.\u003c/p\u003e\n"],["\u003cp\u003eBigQuery repositories are connected to the default Dataform service account and are subject to Dataform quotas, but there are no charges for creating, updating, or deleting a repository.\u003c/p\u003e\n"],["\u003cp\u003eThis is a Pre-GA feature that is subject to the "Pre-GA Offerings Terms" and might have limited support, with feedback and questions directed to bigquery-repositories-feedback@google.com.\u003c/p\u003e\n"]]],[],null,["# Introduction to repositories\n============================\n\n|\n| **Preview**\n|\n|\n| This product or feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA products and features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n| **Note:** To provide feedback or ask questions that are related to this Preview feature, contact [bigquery-repositories-feedback@google.com](mailto:%20bigquery-repositories-feedback@google.com).\n\nThis document helps you understand the concept of repositories in\nBigQuery. You can use repositories to perform version control on\nfiles you use in BigQuery. BigQuery uses Git to record\nchanges and manage file versions.\n\nEach BigQuery repository represents a Git repository. You can\nuse BigQuery's built-in Git capabilities, or you can connect to\na third-party Git repository. Within each repository, you can create one or more\n[workspaces](/bigquery/docs/workspaces-intro) to edit the code stored in the\nrepository.\n\nOn the BigQuery page, your repositories are displayed in\nalphabetical order in the **Repositories** folder of the **Explorer** pane.\n| **Important:** If you create an asset in a BigQuery repository---for example, a query, notebook (including a notebook with an Apache Spark job), BigQuery pipeline, or Dataform workflow---you cannot schedule it for execution in BigQuery repository. For scheduling and executing Dataform pipelines, you need to use Dataform repositories. For scheduling queries and notebooks, use BigQuery Studio. For more information, see [Scheduling queries](/bigquery/docs/scheduling-queries), [Schedule notebooks](/bigquery/docs/orchestrate-notebooks), and [Schedule pipelines](/bigquery/docs/schedule-pipelines).\n\nThird-party repositories\n------------------------\n\nYou can connect a BigQuery repository to\na third-party Git repository if you choose. In this case, the third-party repository stores\nthe repository code instead of BigQuery. BigQuery interacts with the third-party\nrepository to allow you to edit and execute its contents in a\nBigQuery workspace. Depending on the type of repository you\nchoose, you can connect to a third-party repository by using SSH or HTTPS.\n\nThe following table lists supported Git providers and the connection\nmethods that are available for their repositories:\n\nFor more information, see\n[Connect to a third-party repository](/bigquery/docs/repositories#connect-third-party).\n\nService account\n---------------\n\nAll BigQuery repositories are connected to the default\nDataform service account. This service account is derived from your\nproject number in the following format: \n\n service-\u003cvar translate=\"no\"\u003eYOUR_PROJECT_NUMBER\u003c/var\u003e@gcp-sa-dataform.iam.gserviceaccount.com\n\nLocations\n---------\n\nYou can create repositories in all\n[BigQuery Studio locations](/bigquery/docs/locations#bqstudio-loc).\n\nQuotas\n------\n\n[Dataform quotas](/dataform/docs/quotas#quotas) apply to use of\nBigQuery repositories.\n\nPricing\n-------\n\nYou are not charged for creating, updating, or deleting a repository.\n\nFor more information on BigQuery pricing, see [Pricing](/bigquery/pricing).\n\nWhat's next\n-----------\n\n- Learn how to [create repositories](/bigquery/docs/repositories).\n- Learn how to [create workspaces](/bigquery/docs/workspaces)."]]
