What causes TABLE_OR_VIEW_NOT_FOUND?

The table was dropped or renamed upstream in the data pipeline. The query is running in the wrong catalog or schema context (dev vs. prod). A Unity Catalog three-part name (catalog.schema.table) is incorrect or the catalog is not accessible. The table was not yet created by an upstream job that hasn't run yet. A typo in the table name in the SQL code

How do I fix TABLE_OR_VIEW_NOT_FOUND?

Run SHOW TABLES IN to verify the table exists in the expected location. Check the current catalog and schema context with SELECT current_catalog(), current_schema(). Verify the table was created by the upstream pipeline that populates it. If using Unity Catalog, ensure the three-part name (catalog.schema.table) is correct and the catalog is accessible. Check for recent schema changes or table renames in the data pipeline

High severitysql

Power BI Refresh Error:
TABLE_OR_VIEW_NOT_FOUND

What does this error mean?

A SQL query referenced a table or view that does not exist in the current catalog and schema context. This is one of the most common SQL errors in Databricks, often caused by schema drift or environment mismatches.

Common causes

1The table was dropped or renamed upstream in the data pipeline
2The query is running in the wrong catalog or schema context (dev vs. prod)
3A Unity Catalog three-part name (catalog.schema.table) is incorrect or the catalog is not accessible
4The table was not yet created by an upstream job that hasn't run yet
5A typo in the table name in the SQL code

How to fix it

1Run SHOW TABLES IN <schema> to verify the table exists in the expected location
2Check the current catalog and schema context with SELECT current_catalog(), current_schema()
3Verify the table was created by the upstream pipeline that populates it
4If using Unity Catalog, ensure the three-part name (catalog.schema.table) is correct and the catalog is accessible
5Check for recent schema changes or table renames in the data pipeline

Frequently asked questions

Does this error mean the table was deleted?

Not necessarily — it could also mean the query is running in the wrong catalog or schema, or that Unity Catalog permissions prevent the user from seeing the table.

How do I check Unity Catalog permissions?

Use SHOW GRANTS ON TABLE <name> or check the Unity Catalog UI in the Databricks workspace.