databricks-unity-catalog

What problem does it solve?

Unity Catalog governance and visibility require navigating both system tables and volume operations. This skill consolidates best practices for querying audit, lineage, billing, compute, and query history data, plus managing Unity Catalog volumes via the Volumes interface.

Core Features & Use Cases

• System tables guidance: how to read audit logs, table lineage, and billing usage in system tables.
• Volume operations: how to list, upload, download, and manage files in Unity Catalog volumes under /Volumes.
• Governance and visibility: guidelines for governance, access control, and lineage tracking across catalogs and schemas.

Quick Start

Enable system table access and begin exploring volumes:

• Grant necessary access: GRANT USE CATALOG ON CATALOG system TO data_team;
• Query lineage example: SELECT source_table_full_name, target_table_full_name FROM system.access.table_lineage WHERE event_date >= current_date() - 7;
• List volume contents: list volumes in catalog.schema using the Databricks SDK or UI.