POST_START
# Creating, Inspecting, Using, and Managing Unity Catalogs

## Overview

Unity Catalog is a central feature of Databricks that enables you to manage access to data and metadata across your organization. A **catalog** is the top-level container in Unity Catalog, and it provides a way to organize and secure your data assets. In this tutorial, you will learn how to **create, inspect, use, and manage Unity Catalogs** using the `SHOW CATALOGS` operation as the primary focus.

—

## 1. Show Catalogs

To begin, you can list all the catalogs that currently exist in your Databricks workspace using the `SHOW CATALOGS` command. This is the primary operation for this lesson.

“`sql
SHOW CATALOGS;
“`

This query will return a list of all catalogs in your environment. If no catalogs are present, the result will be empty.

—

## 2. Create a Catalog (If Not Exists)

Before you can use a catalog, you must first create it. Use the `CREATE CATALOG IF NOT EXISTS` statement to create a catalog named `training`.

“`sql
CREATE CATALOG IF NOT EXISTS training;
“`

This command ensures that the catalog `training` is created only if it does not already exist.

—

## 3. Describe the Catalog

To inspect the properties of a catalog, use the `DESCRIBE CATALOG` command. This will show you details such as the owner, comment, and other metadata about the catalog.

“`sql
DESCRIBE CATALOG training;
“`

This is useful for understanding the current state of the catalog before making any changes.

—

## 4. Use the Catalog

To switch to a catalog and make it the current one, use the `USE CATALOG` command. This is necessary before performing operations like creating databases or tables within the catalog.

“`sql
USE CATALOG training;
“`

Once you have used the catalog, all subsequent operations will be scoped to it unless explicitly changed.

—

## 5. Check the Current Catalog

You can verify which catalog is currently in use by running the `SELECT current_catalog()` function.

“`sql
SELECT current_catalog();
“`

This is a quick way to confirm that you are working within the correct catalog.

—

## 6. Alter the Catalog Owner

To change the owner of a catalog, use the `ALTER CATALOG` command. This is useful for assigning ownership to a team or role that will manage the catalog.

“`sql
ALTER CATALOG training SET OWNER TO `data_engineers`;
“`

This command transfers ownership of the `training` catalog to the `data_engineers` principal.

—

## 7. Drop the Catalog (If Exists)

If you no longer need a catalog, you can remove it using the `DROP CATALOG IF EXISTS` command.

“`sql
DROP CATALOG IF EXISTS training;
“`

This command will delete the `training` catalog only if it exists. Be cautious with this operation, as it permanently removes the catalog and its contents.

—

## Summary

In this tutorial, you have learned how to:

– Use `SHOW CATALOGS` to list all existing catalogs.
– Create a catalog using `CREATE CATALOG IF NOT EXISTS`.
– Inspect catalog details with `DESCRIBE CATALOG`.
– Switch to a catalog with `USE CATALOG`.
– Verify the current catalog with `SELECT current_catalog()`.
– Change the catalog owner with `ALTER CATALOG`.
– Remove a catalog with `DROP CATALOG IF EXISTS`.

These operations form the foundation of managing Unity Catalogs in Databricks, allowing you to organize and secure your data assets effectively.