이 문서에서는 BigQuery가 사용하는 Google Cloud 서비스와 API를 설명합니다. 또한 이러한 서비스를 사용 중지할 때 BigQuery 동작에 미치는 영향도 설명합니다. 프로젝트에서 서비스를 사용 설정하거나 중지하기 전에 이 문서를 검토하세요.
일부 서비스는 기본적으로 생성되는 모든 Google Cloud 프로젝트에서 사용 설정됩니다.
BigQuery를 사용하는 모든 Google Cloud 프로젝트에 다른 API가 자동으로 사용 설정됩니다. 기능을 사용하기 전에 나머지 서비스를 명시적으로 사용 설정해야 합니다. 자세한 내용은 다음 리소스를 참조하세요.
새 프로필 통계, 데이터 품질 스캔 또는 쿼리 제안을 만들거나 이전에 만든 프로필 통계, 데이터 품질 스캔 또는 쿼리 제안에 액세스할 수 없습니다.
계보 그래프에서 데이터 애셋 세부정보를 확인할 수 없습니다.
데이터 캔버스에서 데이터 애셋을 검색할 수 없습니다.
BigQuery API 사용 중지 영향
BigQuery API를 사용 중지하면 BigQuery API에 종속된 다음 서비스도 사용 중지됩니다.
binaryauthorization.googleapis.com
container.googleapis.com
cloudapis.googleapis.com
dataprep.googleapis.com
servicebroker.googleapis.com
telecomdatafabric.googleapis.com
BigQuery Unified API로 사용 설정된 서비스
BigQuery Unified API(bigqueryunified.googleapis.com)에는 다양한 BigQuery 기능이 작동하는 데 필요한 선별된 서비스 컬렉션이 포함되어 있습니다. BigQuery Unified API를 사용 설정하면 이러한 모든 서비스가 동시에 활성화됩니다. Google은 이 컬렉션의 서비스를 업데이트할 수 있으며 이러한 서비스는 이 API가 사용 설정된 프로젝트에서 자동으로 사용 설정됩니다.
개별 서비스와 API를 사용 중지할 수 있습니다.
bigqueryunified.googleapis.com 사용 설정 방법은 서비스 사용 설정 및 중지를 참조하세요.
BigQuery에서 노트북, 저장된 쿼리와 같은 코드 애셋을 관리하려면 다음 API를 사용 설정해야 합니다.
Compute Engine API
Dataform API
Vertex AI API
2024년 3월 이전에는 이러한 API가 기본적으로 자동으로 사용 설정되지 않았습니다. 2024년 3월 이전에 이러한 API의 상태에 따라 달라지는 자동화 스크립트를 만든 경우 이 스크립트를 업데이트해야 할 수 있습니다. 이러한 API가 이미 사용 설정되어 있으면 BigQuery의 탐색기 창에 새 Notebooks 및 Queries 폴더가 표시됩니다.
시작하기 전에
코드 애셋 관리를 수동으로 사용 설정하려면 Identity and Access Management(IAM) 소유자(roles/owner) 역할이 있어야 합니다.
[[["이해하기 쉬움","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\u003eThis document outlines the various Google Cloud services and APIs that BigQuery relies on, and what happens when you disable them.\u003c/p\u003e\n"],["\u003cp\u003eSeveral services are enabled by default in all new Google Cloud projects, while others are enabled automatically for projects using BigQuery, and some must be enabled manually.\u003c/p\u003e\n"],["\u003cp\u003eDisabling certain services can restrict the ability to manage external connections, create remote models or functions, use the Storage Read or Write API, or access features like data masking.\u003c/p\u003e\n"],["\u003cp\u003eThe BigQuery Unified API (\u003ccode\u003ebigqueryunified.googleapis.com\u003c/code\u003e) allows for a one-click activation of most BigQuery dependent services, ensuring new dependencies are enabled automatically.\u003c/p\u003e\n"],["\u003cp\u003eServices such as \u003ccode\u003ecloudaicompanion.googleapis.com\u003c/code\u003e, \u003ccode\u003ecomposer.googleapis.com\u003c/code\u003e, and \u003ccode\u003edatalineage.googleapis.com\u003c/code\u003e are disabled by default and must be manually enabled for corresponding features like Gemini, scheduled workloads, and data lineage.\u003c/p\u003e\n"]]],[],null,["# Manage BigQuery API dependencies\n================================\n\nThis document describes the Google Cloud services and APIs that\nBigQuery depends on. It also explains the effects on\nBigQuery behavior when you disable those services. Review this\ndocument before you enable or disable services in your project.\n\nSome services are enabled by default in every Google Cloud project that you create.\nOther APIs are automatically enabled for all Google Cloud projects that use\nBigQuery. The remaining services must be explicitly enabled\nbefore you can use their functionality. For more information, see the\nfollowing resources:\n\n- [Services enabled by default](/service-usage/docs/enabled-service#default)\n- [Enabling and disabling services](/service-usage/docs/enable-disable)\n\nThis document is intended for administrators.\n\nServices enabled by default\n---------------------------\n\nThe following services are enabled by default for every new\nGoogle Cloud project:\n\n### Effect of disabling the BigQuery API\n\nDisabling the BigQuery API also disables the following services which are\ndependent upon BigQuery API:\n\n- binaryauthorization.googleapis.com\n- container.googleapis.com\n- cloudapis.googleapis.com\n- dataprep.googleapis.com\n- servicebroker.googleapis.com\n- telecomdatafabric.googleapis.com\n\nServices enabled by BigQuery Unified API\n----------------------------------------\n\nThe BigQuery Unified API (`bigqueryunified.googleapis.com`)\nincludes a curated collection of services that are required for various\nBigQuery features to function. If you enable the\nBigQuery Unified API, then all of these services are activated\nsimultaneously. Google can update the services in this collection, and those\nservices are automatically enabled in projects with this API enabled.\nYou can disable individual services and APIs.\n\nFor instructions on enabling `bigqueryunified.googleapis.com`, see\n[Enabling and disabling services](/service-usage/docs/enable-disable).\n\nServices disabled by default\n----------------------------\n\nYou must manually enable the following services for the corresponding\ncapabilities to become available:\n\nManually enable BigQuery code assets\n------------------------------------\n\nTo manage code assets in BigQuery, such as notebooks and saved queries,\nyou must enable the following APIs:\n\n- The Compute Engine API\n- The Dataform API\n- The Vertex AI API\n\nBefore March 2024, these APIs were not automatically enabled by default. If you\nhave automation scripts from before March 2024 that depended on the status of\nthese APIs, then you might need to update them. If you already have these APIs\nenabled, then you will see new **Notebooks** and **Queries** folders in\nthe **Explorer** pane in BigQuery.\n\n### Before you begin\n\nTo manually enable code asset management,\nyou must have the Identity and Access Management (IAM)\n[Owner (`roles/owner`) role](/iam/docs/understanding-roles#basic).\n\n### Manually enable BigQuery code assets\n\nTo enable required API dependencies for code assets, follow these steps:\n\n1. Go to the **BigQuery** page.\n\n [Go to BigQuery](https://console.cloud.google.com/bigquery)\n2. On the **Studio** , in the tab bar of the editor pane, click the\n arrow_drop_down\n arrow drop-down next to the **+** sign, hold the pointer over **Notebook** ,\n and then select **BigQuery template**.\n\n3. In the banner that appears under the tab bar of the editor pane,\n click **Enable**.\n\n If you don't see the banner, check if you have the required\n IAM [Owner](/iam/docs/understanding-roles#basic) role.\n4. In the **Enable features** pane, in the **Core feature APIs** section,\n do the following:\n\n 1. To enable version history and sharing of code assets, in the **Version history and sharing** section, click **Enable**.\n 2. To enable notebooks, under **Python notebooks** , click **Enable all**.\n 3. When the APIs are enabled, click **Next**.\n5. Optional: Set user permissions in the **Permissions** section:\n\n - To grant principals the ability to create code assets, and to read, edit, and set permissions for the code assets they created, type their user or group names in the **Creator** field.\n - To grant principals the ability to read, edit, and set permissions for all code assets shared with them, type their user or group names in the **Owner** field.\n6. Click **Next**.\n\n7. Optional: In the **Additional APIs** section, click **Enable all** to enable\n the APIs that you need to create BigQuery remote procedures by using\n [BigQuery DataFrames](/python/docs/reference/bigframes/latest).\n\n8. If you chose not to enable the additional APIs, click **Close** to close\n the **Enable features** pane.\n\n### Restrict access to code assets\n\nYou can help prevent enablement of additional APIs by setting the\n[Restrict Resource Service Usage organization policy constraint](/resource-manager/docs/organization-policy/restricting-resources).\nYou can [turn off selected APIs](/service-usage/docs/enable-disable#disabling)\nat any time.\n\nWhat's next?\n------------\n\n- To learn how to manage Google Cloud services, see [Enabling and disabling services](/service-usage/docs/enable-disable).\n- To learn how to manage API access at a granular level with organization policy constraints, see [Restricting resource usage](/resource-manager/docs/organization-policy/restricting-resources).\n- To learn how to control access to services with Identity and Access Management (IAM) roles and permissions for BigQuery, see [BigQuery IAM roles and permissions](/bigquery/docs/access-control)."]]
