What causes QUERY_HISTORY_NOT_ACCESSIBLE?

The user does not have the system.access privilege required to read the query_history system table. System tables have not been enabled by a workspace or account admin. A service principal running an audit or monitoring job was not granted access to the system catalog. The workspace is on a plan that does not include system table access

How do I fix QUERY_HISTORY_NOT_ACCESSIBLE?

Step 1: Verify system tables are enabled: in the Account Console, go to Settings > Feature enablement and confirm system tables are on.. Step 2: Grant the user or service principal the metastore_admin role or a custom role with USE on the system catalog.. Step 3: Run 'GRANT SELECT ON system.access.query_history TO ' using an account admin.. Step 4: For workspace-level history, confirm the user has at least the CAN_VIEW permission on the SQL warehouse.. Step 5: Retry the query; allow a few minutes for grant propagation.

Medium severitypermission

Power BI Refresh Error:
QUERY_HISTORY_NOT_ACCESSIBLE

What does this error mean?

A user or service principal tried to read the Databricks query history system table or the Databricks SQL query history view and was denied because they lack the required role or the system table is not yet enabled.

Common causes

1The user does not have the system.access privilege required to read the query_history system table
2System tables have not been enabled by a workspace or account admin
3A service principal running an audit or monitoring job was not granted access to the system catalog
4The workspace is on a plan that does not include system table access

How to fix it

1Step 1: Verify system tables are enabled: in the Account Console, go to Settings > Feature enablement and confirm system tables are on.
2Step 2: Grant the user or service principal the metastore_admin role or a custom role with USE on the system catalog.
3Step 3: Run 'GRANT SELECT ON system.access.query_history TO <principal>' using an account admin.
4Step 4: For workspace-level history, confirm the user has at least the CAN_VIEW permission on the SQL warehouse.
5Step 5: Retry the query; allow a few minutes for grant propagation.

Frequently asked questions

Are Databricks system tables available on all account plans?

System tables require the Databricks Premium or Enterprise plan with Unity Catalog enabled. They are not available on the legacy Standard plan or workspaces that have not been upgraded to Unity Catalog.

How far back does query history go in the system table?

By default, query history data in system.access.query_history is retained for 365 days. The UI-based query history in Snowsight shows a rolling 90-day window.