To extract metadata and to configure other capabilities that a catalog source might include, you need account access and permissions on the source system. The permissions required might vary depending on the capability.
Permissions to extract metadata
Ensure that you have the required permissions to enable metadata extraction.
•Grant the following permissions for non-unity catalog sources:
- show tables
- show schemas
- describe table extended
- describe schema extended
- show catalogs
•To extract metadata of MCP servers, ensure that the MCP server is registered as a metastore-level connection in the Databricks source system with the is_mcp_connection flag set to true.
•To extract metadata from AI models, grant the following permissions:
- EXECUTE permission on AI models
- USE CATALOG permission on the Databricks Unity Catalog
- USE SCHEMA permission on schemas
•To extract metadata of Databricks Unity Catalog volumes, you need the BROWSE privilege on the Databricks Unity Catalog and the READ VOLUME privilege on the volumes.
•To extract Databricks Unity Catalog lineage with system tables, grant access permissions on the following system tables:
- system.access.column_lineage
- system.access.table_lineage
Note:
If you don't have access to system tables, the metadata extraction job uses REST APIs to extract lineage data.
•To extract Databricks Unity Catalog stored procedure and table metadata with system tables, grant the following permissions on the Databricks Unity Catalog and the system catalog:
- USE CATALOG
- SELECT and USE SCHEMA permissions on the INFORMATION_SCHEMA schema
Note:
To extract metadata of stored procedures, you need permissions on both system.information_schema and catalog.information_schema.
- BROWSE privilege on Databricks Unity Catalog. Required if you don't have the SELECT permission on the Databricks Unity Catalog tables.
When you need to extract metadata from a view associated with a table in a different schema, you must grant the USE SCHEMA permission for the schema that contains the table in Databricks Unity Catalog.
The metadata extraction job uses the following INFORMATION_SCHEMA schema tables to extract metadata:
- TABLES
- COLUMNS
- SCHEMATA
- VIEWS
- KEY_COLUMN_USAGE
- REFERENTIAL_CONSTRAINTS
- CATALOGS
Note:
If you don't have access to the INFORMATION_SCHEMA tables, the metadata extraction job uses the Show and Describe commands to extract metadata.
Permissions to run data profiles
Ensure that you have the required permissions to run profiles.
Grant the following permissions:
•Read permission for Databricks tables in the Databricks source system.
•Access to Databricks workspace and Databricks SQL in the Databricks source system.
Note:
Databricks Unity Catalog governs access to the INFORMATION_SCHEMA schema. To profile the INFORMATION_SCHEMA schema, use a Databricks SQL endpoint and verify that you have the USE and SELECT permissions on the system schemas.
Permissions to perform data classification
You don't need any additional permissions to run data classification.
Permissions to perform relationship discovery
You don't need any additional permissions to run relationship discovery.
Permissions to perform glossary association
You don't need any additional permissions to run glossary association.