The implicit or default data model used by Databricks and Unity Catalog is not Data Vault. Instead, Unity Catalog employs a hierarchical object model to organize and manage data. This hierarchy consists of three levels:
- Catalogs: The top-level containers used to organize data assets, often mirroring organizational units or software development lifecycle scopes.
- Schemas: Also known as databases, these contain tables, views, volumes, AI models, and functions.
- Tables and Views: Tables are collections of data organized by rows and columns, while views are saved queries against one or more tables.
Unity Catalog provides centralized access control, auditing, lineage, and data discovery capabilities across Databricks workspaces. It operates on the principle of least privilege, ensuring users have the minimum access needed to perform their tasks
https://docs.databricks.com/en/data-governance/unity-catalog/index.html
