[[["容易理解","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-08-21 (世界標準時間)。"],[[["\u003cp\u003eThis guide details how to enable the Dataplex API for a Google Cloud project, recommending the creation of a new project per lake instance to keep resources separate.\u003c/p\u003e\n"],["\u003cp\u003eEnabling Dataplex requires selecting or creating a Google Cloud project, ensuring billing is enabled, and enabling the Dataplex, Dataproc, and Dataproc Metastore APIs.\u003c/p\u003e\n"],["\u003cp\u003eDisabling Dataplex requires deleting all lake instances, their assets and zones, and Cloud Storage buckets associated with the lake.\u003c/p\u003e\n"],["\u003cp\u003eBefore disabling the Dataplex API, it is essential to be aware of the potential effects on BigQuery behavior if both are used within the same project.\u003c/p\u003e\n"],["\u003cp\u003eTo disable Dataplex you must go to the enabled API's and services page, locate the Dataplex API and click the disable button.\u003c/p\u003e\n"]]],[],null,["This page explains how to enable or disable Dataplex Universal Catalog for your\nGoogle Cloud project. For information about Service Usage on Google Cloud,\nsee [Enabling and disabling services](/service-usage/docs/enable-disable).\n\nBefore you begin\n\n- [Create a Google Cloud project](/resource-manager/docs/creating-managing-projects)\n and [enable billing](/billing/docs/how-to/manage-billing-account).\n\n- To enable and disable the Dataplex API, you need the\n **Owner** **Editor** role. For more information about roles and permissions,\n see [Access control with IAM](/dataplex/docs/iam-and-access-control).\n\nEnable Dataplex Universal Catalog\n\nYou can use an existing project with Dataplex Universal Catalog or create\na new one. In both cases, you need to enable the\nDataplex API. We recommended that you create a new project.\n\nTo keep resources created by the\nlake within your project, separate from one another, create a project per\nlake instance.\n\nTo create a project and enable Dataplex Universal Catalog, follow these steps:\n\n1. In the Google Cloud console, [select or create a project](https://console.cloud.google.com/cloud-resource-manager).\n2. Make sure that [billing is enabled](/billing/docs/how-to/modify-project) for your project.\n3.\n\n\n Enable the Dataplex, Dataproc, and Dataproc Metastore APIs.\n\n\n [Enable the APIs](https://console.cloud.google.com/flows/enableapi?apiid=dataplex.googleapis.com,dataproc.googleapis.com,metastore.googleapis.com)\n | **Note:** If you also enable the [Data Lineage API](/dataplex/docs/about-data-lineage), it incurs charges separately from the Dataplex API. For more information, see [Dataplex Universal Catalog pricing](/dataplex/pricing) and [Data lineage considerations](/dataplex/docs/lineage-considerations).\n\nDisable Dataplex Universal Catalog\n\nIf you use Dataplex Universal Catalog in a project that also uses BigQuery,\nbe aware of the\n[effects on BigQuery behavior](/bigquery/docs/service-dependencies)\nwhen you disable Dataplex Universal Catalog.\n\nTo avoid additional charges, complete the following steps before you disable\nDataplex Universal Catalog:\n\n1. In the Google Cloud console, delete each lake instance in your project.\n To delete a lake, you must first delete the individual assets and zones. For\n more information, see [Delete a lake](/dataplex/docs/manage-lake#deleting-a-lake).\n\n | To avoid charges, delete all Cloud Storage buckets for zones within your\n | lake. You can delete the Cloud Storage buckets before or after disabling\n | the API.\n |\n | Wait until in-progress service operations for deleting lakes complete.\n | Look for an empty list of lake instances on the Dataplex Universal Catalog page.\n2. In the Google Cloud console, delete all custom entry groups in your project. Deleting an entry group removes all entries that belong to the entry group. For more information, see [Delete Entry Group](/dataplex/docs/ingest-custom-sources#delete-entry-group).\n\n3. Select the project to disable the Dataplex API in.\n\n4. Go to the **Enabled APIs \\& services** page.\n\n\n [Go to Enabled APIs \\& services](https://console.cloud.google.com/apis/dashboard)\n\n \u003cbr /\u003e\n\n5. Click **Cloud Dataplex API**.\n\n6. Click **Disable API**. Confirm when prompted.\n\n7. To disable the following APIs, repeat the steps:\n\n - Data Lineage API (if enabled)\n\nWhat's next?\n\n- Learn how to [search for resources](/dataplex/docs/search-assets).\n- Learn how to [measure data quality](/dataplex/docs/auto-data-quality-overview).\n- Learn about [catalog management concepts](/dataplex/docs/catalog-overview).\n- Follow a quickstart: [Track data lineage for a BigQuery table](/dataplex/docs/track-lineage-quickstart)."]]
