metricsign
Start free
High severityschema

Power BI Refresh Error:
1146

What does this error mean?

The referenced table does not exist in the current database — often caused by a missing migration or schema drift.

Common causes

  • 1A dbt model or migration that creates the table has not been run
  • 2The table was dropped accidentally or by a failed migration
  • 3The query references the wrong schema/database prefix
  • 4Case sensitivity mismatch on Linux MySQL (table name case differs from filesystem)

How to fix it

  1. 1Step 1: Verify the table exists: `SHOW TABLES LIKE 'your_table';`
  2. 2Step 2: Check if the table is in a different database: `SELECT table_schema, table_name FROM information_schema.tables WHERE table_name='your_table';`
  3. 3Step 3: Re-run the migration or dbt model that creates the table: `dbt run --select your_model`.
  4. 4Step 4: If deleted accidentally, restore from backup or recreate from the DDL in version control.

Frequently asked questions

Why does my table exist in SHOW TABLES but MySQL still returns 1146?

Check for case sensitivity — on Linux, `Orders` and `orders` are different tables. Also verify you are connected to the correct database with `SELECT DATABASE();`

How can dbt cause MySQL error 1146?

If a dbt model fails partway through and drops the staging table before recreating it, downstream ADF or Power BI queries targeting that table will get error 1146 until dbt completes successfully.

Can MetricSign correlate a dbt failure with a subsequent Power BI refresh failure?

Yes — MetricSign's lineage feature links dbt job failures to downstream Power BI dataset refresh failures, showing the full impact chain.

Official documentation: https://dev.mysql.com/doc/mysql-errors/8.0/en/server-error-reference.html

Other schema errors