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 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 table metadata with system tables, you need the following permissions:
- USE CATALOG permission on the Databricks Unity Catalog
- SELECT and USE SCHEMA permissions on the INFORMATION_SCHEMA schema
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.
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.