USE CATALOG and USE SCHEMA: alone they expose no data, yet reaching any object inside requires them, so owners of catalogs and schemas can cap what table owners share.
Also called USE CATALOG, USE SCHEMA.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Usage privileges in context, with comparison tables and the common traps.
Terms in this definition
- Event
Table in Log Analytics where entries from Windows event logs are kept.
- Share
In OpenSharing, the container you fill with tables, views, volumes, models and notebooks for recipients. You need
CREATE SHAREon the metastore to make one; add a schema and all its assets, including later ones, go with history.
Related terms
- BROWSE
Granted on a catalog, this Unity Catalog privilege lets people discover objects, read their metadata and request access, all without
USE CATALOGand with no access to the data itself. - EXECUTE
Allows calling a function or loading a registered model in Unity Catalog, and seeing its definition.
USE CATALOGandUSE SCHEMAare needed too. - Schema
The middle part of a Unity Catalog name (
catalog.schema.table), grouping tables, views, volumes, functions and models inside a catalog. A grant on it covers everything in it now and later, and nothing inside can be reached withoutUSE SCHEMA. - System tables
Operational data about your account, held read-only in the
systemcatalog, e.g.system.access.audit,system.billing.usageand lineage. Users needSELECTplusUSE CATALOGandUSE SCHEMA.