Programatically enabling system tables for Databricks


Since system tables are governed by Unity Catalog, you need at least one Unity Catalog-governed workspace in your account to enable system tables. That way you can map your system tables to the Unity Catalog metastore. System tables must be enabled by an **account admin**. You can enable system tables in your account using the Databricks CLI, the Databricks SDK for Python, or by calling the Unity Catalog API in a notebook.




You can enable system tables using API calls or directly in a Databricks notebook (such as this example). Please refer to the documentation for your cloud for further details ([AWS](https://docs.databricks.com/administration-guide/system-tables/index.html) | [Azure](https://learn.microsoft.com/en-us/azure/databricks/administration-guide/system-tables/))


**Running this notebook will enable the system tables and you will see them in your system catalog.**



Creating the widget to be used as input for the metastore ID


The metastore ID can be found by clicking on the metastore details icon present in the `Data` tab of your Databricks workspace.
![metastore_id_image](./images/metastore_id.png)

Enabling schemas


Use Python SDK and the workspace client to authenticate, identify available schemas, and enable those schemas