Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Mengelola dependensi BigQuery API
Dokumen ini menjelaskan layanan dan API Google Cloud yang digunakan BigQuery. Dokumen ini juga menjelaskan efek pada
perilaku BigQuery saat Anda menonaktifkan layanan tersebut. Tinjau dokumen ini sebelum Anda mengaktifkan atau menonaktifkan layanan di project Anda.
Beberapa layanan diaktifkan secara default di setiap project Google Cloud yang Anda buat.
API lainnya diaktifkan secara otomatis untuk semua Google Cloud project yang menggunakan
BigQuery. Layanan yang tersisa harus diaktifkan secara eksplisit
sebelum Anda dapat menggunakan fungsinya. Untuk informasi selengkapnya, lihat referensi berikut:
Anda tidak dapat membuat atau mengakses insight profil, pemindaian kualitas data, atau saran kueri yang dibuat sebelumnya.
Anda tidak dapat melihat detail aset data pada grafik silsilah.
Anda tidak dapat menelusuri aset data di kanvas data.
Efek menonaktifkan BigQuery API
Menonaktifkan BigQuery API juga akan menonaktifkan layanan berikut yang bergantung pada BigQuery API:
binaryauthorization.googleapis.com
container.googleapis.com
cloudapis.googleapis.com
dataprep.googleapis.com
servicebroker.googleapis.com
telecomdatafabric.googleapis.com
Layanan yang diaktifkan oleh BigQuery Unified API
BigQuery Unified API (bigqueryunified.googleapis.com)
mencakup kumpulan layanan pilihan yang diperlukan agar berbagai fitur BigQuery berfungsi. Jika Anda mengaktifkan
BigQuery Unified API, semua layanan ini akan diaktifkan
secara bersamaan. Google dapat mengupdate layanan dalam koleksi ini, dan layanan tersebut akan otomatis diaktifkan di project yang mengaktifkan API ini.
Anda dapat menonaktifkan setiap layanan dan API.
Model jarak jauh BigQuery ML yang ada akan berhenti
berfungsi.
Notebook yang ada tetap dapat diakses untuk diedit.
bigqueryunified.googleapis.com
Menyediakan aktivasi layanan dependen BigQuery dengan sekali klik yang tercantum dalam dokumen ini, kecuali API cloudaicompanion, composer, dan datalineage.
Memastikan dependensi BigQuery baru diaktifkan di
project Anda.
Dependensi mendatang tidak otomatis diaktifkan di project Anda.
compute.googleapis.com
Google Compute Engine menyediakan lingkungan runtime untuk semua
fitur yang disediakan oleh Dataproc dan Vertex AI.
Notebook Colab, model ML jarak jauh, tugas Apache Spark, SparkSQL, dan PySpark akan berhenti.
Untuk mengelola aset kode di BigQuery, seperti notebook dan kueri tersimpan, Anda harus mengaktifkan API berikut:
Compute Engine API
Dataform API
Vertex AI API
Sebelum Maret 2024, API ini tidak diaktifkan secara otomatis secara default. Jika Anda memiliki skrip otomatisasi dari sebelum Maret 2024 yang bergantung pada status API ini, Anda mungkin perlu memperbaruinya. Jika sudah mengaktifkan API ini, Anda akan melihat folder Notebooks dan Queries baru di panel Explorer di BigQuery.
Sebelum memulai
Untuk mengaktifkan pengelolaan aset kode secara manual,
Anda harus memiliki peran Pemilik (roles/owner) pada Identity and Access Management (IAM).
Mengaktifkan aset kode BigQuery secara manual
Untuk mengaktifkan dependensi API yang diperlukan untuk aset kode, ikuti langkah-langkah berikut:
Di Studio, di panel tab panel editor, klik
arrow_drop_down
drop-down panah di samping tanda +, arahkan kursor ke Notebook,
lalu pilih Template BigQuery.
Di banner yang muncul di bawah panel tab editor,
klik Aktifkan.
Jika Anda tidak melihat banner tersebut, periksa apakah Anda memiliki peran Pemilik IAM yang diperlukan.
Di panel Enable features, di bagian Core feature APIs,
lakukan tindakan berikut:
Untuk mengaktifkan histori versi dan berbagi aset kode,
di bagian Histori versi dan berbagi, klik Aktifkan.
Untuk mengaktifkan notebook, di bagian Python notebooks, klik Enable all.
Setelah API diaktifkan, klik Next.
Opsional: Tetapkan izin pengguna di bagian Permissions:
Untuk memberi akun utama kemampuan membuat aset kode, serta membaca, mengedit, dan menetapkan izin untuk aset kode yang mereka buat, ketik nama pengguna atau grup di kolom Creator.
Untuk memberi akun utama kemampuan membaca, mengedit, dan menetapkan izin untuk semua aset kode yang dibagikan kepada mereka, ketik nama pengguna atau grup di kolom Pemilik.
Klik Berikutnya.
Opsional: Di bagian Additional APIs, klik Enable all untuk mengaktifkan API yang diperlukan untuk membuat prosedur jarak jauh BigQuery menggunakan BigQuery DataFrames.
Jika Anda memilih untuk tidak mengaktifkan API tambahan, klik Close untuk menutup panel Enable features.
Untuk mempelajari cara mengelola akses API pada tingkat terperinci dengan batasan kebijakan
organisasi, lihat
Membatasi penggunaan resource.
Untuk mempelajari cara mengontrol akses ke layanan dengan
peran dan izin Identity and Access Management (IAM) untuk
BigQuery, lihat
Peran dan izin IAM BigQuery.
[[["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\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)."]]
