POST_START
# 02. Schema Basics

In this lesson, we will explore the basics of working with **schemas** in Databricks Unity Catalog. A schema is a logical container for organizing your data assets, such as tables, views, and volumes. Understanding how to create, describe, and manage schemas is essential for maintaining a well-structured and secure data environment.

—

## 1. Creating a Schema

The first step in working with schemas is to **create** one if it does not already exist. This is done using the `CREATE SCHEMA IF NOT EXISTS` command.

### ✅ Primary Operation
“`sql
CREATE SCHEMA IF NOT EXISTS training.sales;
“`

This command creates a schema named `sales` within the `training` catalog, if it does not already exist. This is a safe way to ensure that your schema is available without risking errors from duplicate creation.

—

## 2. Verifying the Schema Exists

After creating the schema, it's useful to verify that it exists in the catalog. You can do this using the `SHOW SCHEMAS IN training;` command.

### ✅ Allowed SQL Step
“`sql
SHOW SCHEMAS IN training;
“`

This will list all schemas in the `training` catalog. You should see `sales` in the output if it was successfully created.

—

## 3. Describing the Schema

Once the schema exists, you may want to inspect its properties. The `DESCRIBE SCHEMA` command provides metadata about a schema, including its name, catalog, and owner.

### ✅ Allowed SQL Step
“`sql
DESCRIBE SCHEMA training.sales;
“`

This command will return information about the `sales` schema, such as its location, comment, and owner. It is a useful tool for verifying schema details and understanding its configuration.

—

## 4. Switching Context to the Catalog and Schema

In Databricks, you can switch your current context to a specific catalog or schema using the `USE` command. This makes it easier to reference objects within that context.

### ✅ Allowed SQL Steps
“`sql
USE CATALOG training;
USE SCHEMA sales;
“`

These commands change your current catalog to `training` and your current schema to `sales`. Once you're in this context, you can reference tables and other objects without specifying the full catalog and schema name.

—

## 5. Checking the Current Schema

You can also check what schema you're currently in using the `SELECT current_schema();` command.

### ✅ Allowed SQL Step
“`sql
SELECT current_schema();
“`

This will return the name of the current schema, which is helpful for debugging or verifying your context.

—

## 6. Changing the Owner of a Schema

In some cases, you may need to change the owner of a schema, especially when transitioning from one team to another. This can be done using the `ALTER SCHEMA` command.

### ✅ Allowed SQL Step
“`sql
ALTER SCHEMA training.sales SET OWNER TO `data_engineers`;
“`

This command changes the owner of the `sales` schema to the user or group `data_engineers`. This is a common operation when reassigning access or responsibility for a schema.

—

## 7. Removing a Schema (if Needed)

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

### ✅ Allowed SQL Step
“`sql
DROP SCHEMA IF EXISTS training.sales;
“`

This command safely deletes the `sales` schema from the `training` catalog, if it exists. Use this with caution, as it permanently removes the schema and all its contents.

—

## Summary

In this lesson, you've learned the following:

– How to **create a schema** using `CREATE SCHEMA IF NOT EXISTS`.
– How to **verify the existence** of a schema with `SHOW SCHEMAS IN`.
– How to **describe a schema** with `DESCRIBE SCHEMA`.
– How to **switch context** to a catalog and schema using `USE`.
– How to **check the current schema** with `SELECT current_schema();`.
– How to **change the owner** of a schema with `ALTER SCHEMA`.
– How to **remove a schema** using `DROP SCHEMA IF EXISTS`.

These operations are fundamental to working with Unity Catalog in Databricks and will be used throughout your data engineering workflow. In the next lesson, we will explore how to manage tables and volumes within schemas.