What causes 002043 (02000)?

Object name is misspelled or uses incorrect case (Snowflake stores unquoted identifiers as uppercase). The object was dropped or renamed before the query ran. The query targets a different database or schema than expected (missing USE DATABASE / USE SCHEMA). The executing role lacks SELECT or REFERENCES privilege on the object, causing Snowflake to report it as non-existent. A view or materialized view references a base table that was dropped

How do I fix 002043 (02000)?

Verify the object exists: SHOW TABLES LIKE 'my_table' IN SCHEMA mydb.myschema. Check identifier casing: unquoted identifiers are stored uppercase; 'my_table' and 'MY_TABLE' are the same, but '"my_table"' (quoted) is case-sensitive. Confirm the active database and schema: SELECT CURRENT_DATABASE(), CURRENT_SCHEMA(). Use fully-qualified names to avoid context dependency: mydb.myschema.my_table. If the object exists but the error persists, the role likely lacks visibility — grant SELECT: GRANT SELECT ON TABLE mydb.myschema.my_table TO ROLE my_role

Medium severityexecution

Power BI Refresh Error:
002043 (02000)

What does this error mean?

The referenced database object (table, view, schema, stage, or stream) does not exist in the current context, or the executing role lacks the privilege to see it. Snowflake deliberately uses the same error for both cases to avoid information leakage.

Common causes

1Object name is misspelled or uses incorrect case (Snowflake stores unquoted identifiers as uppercase)
2The object was dropped or renamed before the query ran
3The query targets a different database or schema than expected (missing USE DATABASE / USE SCHEMA)
4The executing role lacks SELECT or REFERENCES privilege on the object, causing Snowflake to report it as non-existent
5A view or materialized view references a base table that was dropped

How to fix it

1Verify the object exists: SHOW TABLES LIKE 'my_table' IN SCHEMA mydb.myschema
2Check identifier casing: unquoted identifiers are stored uppercase; 'my_table' and 'MY_TABLE' are the same, but '"my_table"' (quoted) is case-sensitive
3Confirm the active database and schema: SELECT CURRENT_DATABASE(), CURRENT_SCHEMA()
4Use fully-qualified names to avoid context dependency: mydb.myschema.my_table
5If the object exists but the error persists, the role likely lacks visibility — grant SELECT: GRANT SELECT ON TABLE mydb.myschema.my_table TO ROLE my_role

Frequently asked questions

How do I find out if an object was recently dropped?

Check Snowflake's access history: SELECT * FROM SNOWFLAKE.ACCOUNT_USAGE.ACCESS_HISTORY WHERE QUERY_TYPE = 'DROP' ORDER BY QUERY_START_TIME DESC. You can also use SHOW TERSE OBJECTS IN SCHEMA ... to list surviving objects.

Why does Snowflake give the same error for 'missing' and 'no permission'?

This is a deliberate security design — revealing whether an object exists to an unauthorized role would leak schema information. Treat error 002043 as either 'does not exist' or 'no access' until you verify both.