Creating a Unity Catalog catalog that matches the workspace needs

In Azure Databricks, a catalog is the top-level container in the Unity Catalog three-level namespace (catalog.schema.table) and is created to logically separate data by business unit, environment, or workspace. Catalog creation requires Unity Catalog to be enabled on the metastore and the creator to have the CREATE CATALOG privilege, and the resulting catalog should be configured with appropriate managed storage location and ownership to meet governance requirements.

1 · Learn the must-know

• 1A catalog can only be created if the metastore admin or a user/group has been granted the CREATE CATALOG privilege on the Unity Catalog metastore.
• 2You can create a catalog using CREATE CATALOG <name> in SQL, via the Catalog Explorer UI, or with the Databricks CLI/API/Terraform, optionally specifying a MANAGED LOCATION for default storage.
• 3Specifying a managed storage location for a catalog requires an existing external location and storage credential configured in Unity Catalog; if omitted, the catalog inherits the metastore's default storage location.
• 4By default the catalog creator becomes its owner, but ownership can and often should be reassigned to a group for shared administration and to avoid a single point of failure.
• 5Catalogs can be created as standard or as a foreign catalog (for Lakehouse Federation to external systems) or as a shared catalog for Delta Sharing, depending on the data source and access requirements.
• 6Binding a catalog to specific workspaces via workspace-catalog bindings lets you restrict which workspaces can access it, which is important when designing catalogs to isolate environments like dev, staging, and production.

2 · Check your understanding