POST_START
# Databricks Unity Catalog Tutorial: 01. Catalog Basics

In this tutorial, we will explore the basics of Unity Catalog in Databricks. Unity Catalog is a centralized metadata service that helps manage access to data assets across your organization. One of the foundational operations in Unity Catalog is **SHOW CATALOGS**, which allows you to list all the catalogs available in your Databricks workspace.

—

## 1. Show All Catalogs

The first step in working with Unity Catalog is to view the list of existing catalogs. This can be done using the `SHOW CATALOGS;` command. This statement returns a list of all catalogs that have been created in your Databricks workspace.

“`sql
SHOW CATALOGS;
“`

This command is useful for verifying the current state of your catalog environment and for identifying any existing catalogs that you may need to work with.

—

## 2. Create a New Catalog

If the catalog you are looking for does not exist, you can create a new one using the `CREATE CATALOG IF NOT EXISTS` command. This ensures that a catalog is created only if it does not already exist, preventing duplicate catalog creation.

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

This command creates a catalog named `training` if it does not already exist. It is a safe way to initialize a new catalog for your data workflows.

—

## 3. Describe a Catalog

To get more information about a catalog, such as its owner and other metadata, you can use the `DESCRIBE CATALOG` command. This provides a detailed description of the catalog's properties.

“`sql
DESCRIBE CATALOG training;
“`

This command is particularly useful for verifying the configuration of a catalog and understanding its current state.

—

## 4. Use a Catalog

Once a catalog is created, you can switch to it using the `USE CATALOG` command. This sets the current catalog context for subsequent operations, such as creating databases or tables.

“`sql
USE CATALOG training;
“`

By setting the current catalog, you ensure that all subsequent operations are performed within the context of the specified catalog.

—

## 5. Check Current Catalog

To confirm which catalog is currently in use, you can run the `SELECT current_catalog();` command. This returns the name of the catalog that is currently active in your session.

“`sql
SELECT current_catalog();
“`

This is a helpful command for verifying your catalog context, especially when working in a shared or multi-catalog environment.

—

## 6. Alter a Catalog

To change the owner of a catalog, you can use the `ALTER CATALOG` command. This is useful for managing access and permissions across your organization.

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

This command changes the owner of the `training` catalog to the `data_engineers` user or group. It is an essential part of managing access and accountability in a collaborative environment.

—

## 7. Drop a Catalog

If you no longer need a catalog, you can remove it using the `DROP CATALOG IF EXISTS` command. This ensures that the catalog is deleted only if it exists, preventing errors.

“`sql
DROP CATALOG IF EXISTS training;
“`

This command is useful for cleaning up your environment and removing unnecessary catalogs that are no longer in use.

—

## Summary

In this tutorial, you have learned the fundamentals of working with Unity Catalog in Databricks. You have explored how to:

– List all available catalogs using `SHOW CATALOGS;`
– Create a new catalog with `CREATE CATALOG IF NOT EXISTS training;`
– Describe a catalog using `DESCRIBE CATALOG training;`
– Switch to a catalog with `USE CATALOG training;`
– Check the current catalog with `SELECT current_catalog();`
– Alter a catalog's owner with `ALTER CATALOG training SET OWNER TO `data_engineers`;`
– Remove a catalog with `DROP CATALOG IF EXISTS training;`

These commands form the foundation of catalog management in Unity Catalog, and they are essential for organizing and securing your data assets in Databricks.