ODBC: ERROR [02000]

Hi, 

I resolved by changing snowfalke query to native queries. 

let
Source = Value.NativeQuery(Snowflake.Databases("XX.azure.snowflakecomputing.com",
"TEST_QUERY",[Role="TEST"]){[Name="TEST"]}[Data],
"select * from ""GOLD"".""SHIFT""", null, [EnableFolding=true]),
#"Removed Columns" = Table.RemoveColumns(Source,{"ETL_UPDATE_JOB_NAME","People ID Masked Roster End Date Key", "ETL_ROW_EXPIRY_DATE", "ETL_ROW_CURRENT_FLAG", "ETL_INSERT_DATETIME", "ETL_UPDATE_DATETIME", "ETL_INSERT_JOB_NAME"})
in
#"Removed Columns"

/*let
Source = Snowflake.Databases("XX.azure.snowflakecomputing.com", #"Snowflake-WH", [Role= #"Snowflake-WH", CreateNavigationProperties=null, ConnectionTimeout=null, CommandTimeout=null]),
Database = Source{[Name=#"Snowflake-DB",Kind="Database"]}[Data],
GOLD_Schema = Database{[Name="GOLD",Kind="Schema"]}[Data],
#"SHIFT_View" = GOLD_Schema{[Name="SHIFT",Kind="Table"]}[Data]
in
SHIFT_View*/

Also, changed number of parrallel load.

Hi Anonymous ,

Thanks for reaching out us. After some researching, I think the problem arises because of the data source, not the Desktop.

I found this similar post with the same error message.

Error: 002043 (02000): SQL compilation error: Object does not exist, or operation cannot be performed · Issue #892 · Snowflake-Labs/terraform-provider-snowflake · GitHub

The user found out that renaming between lowercase and uppercase causes mapping issues in snowflake.

What he did in the end was I just deleted the resources from the state file.

Hope this can help you~

Best Regards,

Stephen Tao

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

We recently starting getting the same message too.  But the error only seems to show up in PowerBI Desktop.  The nightly refreshes in our service work just fine.  As was mentioned, we did find that switching to native queries does work.  But we don't consider this a long term solution.  It feels like there has been some recent change that has caused this.  

Note - our admin noticed that if you just hit refresh a couple of times, it eventually works.  But it will error again in the future.