Connecting to Snowflake DB, warehouse not recognised error

[GosiaK]

Hi All,

I'm connecting through Alteryx Designer to external (client's) Snowflake DB for the first time.

I've installed Simba driver and configured ODBC DataSource Administrator with info provided by client, including warehouse id, test was Successful, it said connected to data source.

But when I try to set up the input tool, using this connection, I got the following error: 

Error SQLExecute: No active warehouse selected in the current session.  Select an active warehouse with the 'use warehouse' command.¶

I found on Alteryx community that warehouse can be specified in Pre SQL Stetement, so I did that, but getting following error:

Error running PreSQL: "use warehouse XXX;": SQL compilation error:¶Object does not exist, or operation cannot be performed.

Below is the configuration.

Could someone smart please advise where I'm going wrong?

 

[davidskaife]

Hi @GosiaK 

Providing you've set the ODBC driver up correctly, I'd say this is more a Snowflake issue rather than an Alteryx one. A big one to check is does the User Credentials you're using to connect have permissions in Snowflake to use that Warehouse?

[GosiaK]

Thanks @davidskaife for quick answer. Is there anyway I could check this from Alteryx side, before I get on to client to check Snowflake from their side? The user credentials have been given to us by the client, so it was just copy and paste on our side.

[davidskaife · Accepted solution]

Hi @GosiaK 

I don't think so, beyond double checking everything has been entered correctly in the ODBC Settings, the connection itself etc

The ODBC connection tests that you can connect, which is working, but the process fails in Alteryx which uses credentials to which permissions would need to be granted would potentially suggest that is the cause. However someone else far more knowledgeable than me may chime in with help! 

@apathetichell any thoughts?

[ArunMukkaraLYB]

Hello there, we are also facing the same issue. Did you manage to resolve the issue? Please let me know! Thanks in advance.

[zcdavis]

Have you attempted to perform the same query utilizing snowflake?

The potential issue I see is the path isn't available in the written warehouse. The format of the Pre Create SQL Statement looks correct as long as it's ending in ";". Ensure that you have the privileges to use that warehouse and perform that query prior to attempting the same pull in Alteryx.

[apathetichell]

Hey --- just saw this thread --- and belated thanks to @davidskaife for sharing... 1 ---> yes this reads like a Snowflake issue ---> not an Alteryx issue. I would double check this in a few ways:

1) Does the user you are authenticating as have access to the warehouse in Snowflake?

2) Do they have a default warehouse?

3) What do the Snowflake logs say?

4) If you are using ODBC 64 for a connection ---> throw in the warehouse and hit test.

5) remove the warehouse and hit test --> real talk --- you do not need to specify a warehouse if you have a default warehouse.

[apathetichell]

If use warehouse xxxx; in presql gives you an issue --- you can try -> SHOW WAREHOUSES;  -> in your SQL and see what shoes up.

[tom979]

Im having the same error.

Configuration:  Snowflake oAuth

Alteryx  seems to have Warehouse set to NULL (run a select current_warehouse() as my query)

a command show warehouses doesn't show all the warehouses accessible by the user.

Are you guys all using Snowflake oAuth for authentication?  I could never get the Entra ID(AD Private) integration to work properly through Azure.

[apathetichell]

I have never used Snowflake OAUTH with Alteryx. I prefer to never touch Snowflake Oauth. Can you use externalbrowser vs oauth? externalbrowser (SAML) is the standard for browser based auth with Snowflake and Alteryx --- not Oauth. Oauth is really webapp to webapp vs desktop system to Snowflake.

You'll also need to like provide the error messages.