Skip to content
datastudyguides

DP-750 · 1.2.1 · Set up and configure an Azure Databricks environment

Unity Catalog naming

Apply naming conventions based on requirements, including isolation, development environment, and external sharing

Design catalog and schema names around governance boundaries, environments, teams, and sharing needs.

Design the namespace first

Infographic explaining Unity Catalog naming conventions, environment separation, automation, and sharing boundaries.

Use predictable catalog and schema names that reflect ownership and isolation. Consistency makes permissions, automation and deployment easier to reason about.

See the real object model

Microsoft Learn Unity Catalog object model showing the metastore, catalogs, schemas, tables, views, volumes, functions, models, and services.

Unity Catalog uses a three-level namespace for governed assets: catalog.schema.object. Catalogs are a strong boundary for environment or workspace isolation; schemas are a useful boundary for domains and teams.

Keep sharing intentional

  • Separate dev, test, and prodSeparate catalogs
  • Group one domain or teamSchema
  • Expose shared dataClearly named shared boundary
Naming boundary

Names should reveal the intended boundary without requiring tribal knowledge.

Key points

  • Catalog: Strong governance and isolation boundary
  • Schema: Organizes related data products inside a catalog
  • Environment: Separate dev, test, and prod deliberately
  • Sharing: Use clear ownership and external-sharing boundaries

Exam trap

Do not encode every organizational detail into table names when catalog and schema already provide hierarchy.

Sources · 1 Microsoft Learn page Show ▾

Checked on October 4, 2026. Report a problem

Go deeper on Microsoft Learn

Checked against Microsoft Learn on October 4, 2026. Report a problem with this card

How well do you know this?