This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowThe Fabric community is upgrading! Read all of the details including the timeline and what you can expect. Learn more
Hi,
I have made sure that I have set up the role and warehouse and they have the necessary priviledge, etc. to access to the database, schema and view in our Snowflake account. However, I kept getting errors like below:
ADBC: NotFound [] [Snowflake] 002003 (42S02): SQL compilation error: Table 'database.schema.VIEW' does not exist or not authorized.
Sometimes the errors are there for certain views; sometimes they are gone -- that is to say, the errors are randomly showing up on the views. Also, we are using Power BI Desktop Version: 2.145.1105.0 64-bit (July 2025)
Any ideas on the root cause of this?
Thanks!
Solved! Go to Solution.
The intermittent "Table Not Found" error when accessing Snowflake views in Power BI is usually caused by the active role not having proper access or not being set during the session. To resolve this, ensure the correct role is set as active using USE ROLE your_role; in Power BI's advanced options. Also, grant SELECT privileges on all underlying tables or views used within the Snowflake view to that role. Clear Power BI's cache from File > Options and settings > Options > Data Load > Clear Cache, and make sure object names are consistently cased to avoid case-sensitivity issues.
The intermittent "Table Not Found" error when accessing Snowflake views in Power BI is usually caused by the active role not having proper access or not being set during the session. To resolve this, ensure the correct role is set as active using USE ROLE your_role; in Power BI's advanced options. Also, grant SELECT privileges on all underlying tables or views used within the Snowflake view to that role. Clear Power BI's cache from File > Options and settings > Options > Data Load > Clear Cache, and make sure object names are consistently cased to avoid case-sensitivity issues.
Thank you. Clearing Power BI Cache seems to solve the problem!
Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.
| User | Count |
|---|---|
| 24 | |
| 22 | |
| 20 | |
| 18 | |
| 14 |
| User | Count |
|---|---|
| 32 | |
| 26 | |
| 23 | |
| 20 | |
| 20 |