MetricSign
EN|NLRequest Access
High severitysql

Power BI Refresh Error:
SCHEMA_NOT_FOUND

What does this error mean?

The SQL statement references a schema (database) that does not exist in the current catalog. The query is rejected at parse time — no data is read.

Common causes

  • 1A schema was dropped or renamed in Unity Catalog without updating downstream queries
  • 2The query is running against the wrong catalog (dev vs. prod) where the schema does not exist
  • 3A Unity Catalog schema name change during a migration was not propagated to all jobs
  • 4The schema was never created in the new environment after a workspace migration
  • 5A typo in the schema name in the SQL code or job configuration

How to fix it

  1. 1Run SHOW SCHEMAS IN <catalog> to confirm the available schemas in the current catalog
  2. 2Check the current catalog context: SELECT current_catalog()
  3. 3If using Unity Catalog three-part names, verify catalog.schema.table is correct
  4. 4Re-create the schema if it was accidentally dropped: CREATE SCHEMA IF NOT EXISTS <name>
  5. 5Update the job configuration or SQL query to use the correct schema name

Frequently asked questions

Is SCHEMA_NOT_FOUND the same as DATABASE_NOT_FOUND?

Yes — in Databricks, SCHEMA and DATABASE are synonyms. SCHEMA_NOT_FOUND and DATABASE_NOT_FOUND refer to the same object type.

Can a schema be missing due to permissions rather than not existing?

Yes — if a Unity Catalog schema exists but the user or service principal lacks USAGE privilege, it appears to not exist. Grant USAGE ON SCHEMA to the running principal.

Other sql errors