BigQuery Unified API (bigqueryunified.googleapis.com) 包含各種 BigQuery 功能運作所需的精選服務。啟用 BigQuery Unified API 後，所有這些服務都會一併啟用。Google 可以更新這個集合中的服務，且這些服務會在啟用此 API 的專案中自動啟用。您可以停用個別服務和 API。
[[["容易理解","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 (世界標準時間)。"],[[["\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)."]]
