Snowflake Bulk Loader

[kcampbell91]

Hello, 

I am running into an issue using the Snowflake Bulk Loader in the output tool.  I have downloaded the SnowflakeDSIIDrvier, established a DSN, confirmed it connects.  Then when loading a table for the first time, I am able to "Create" a table through Alteryx in Snowflake however no data is actually being sent.  The Alteryx workflow continues to spin and spin, but never ends either so I do not have an error message.  

I set this up a few months ago during our Snowflake POC and the Snowflake bulk loader worked fine, no issues.  Now when I go to run the same exact workflows with the same set up, no data is being sent.  I can create a new table, but not add, delete, append anything with the data.  Our Snowflake solutions architect checked Snowflake and confirmed that there is no file / data entering Snowflake.

I have tried the ODBC connection as well and that works fine.  I can send the data with no issues, however that is not ideal because it takes forever.

Has anyone had this issue and how did you resolve it?  It's obviously communicating because it creates a table, but it's driving me crazy the data is not being sent.

Is this an Alteryx or a Snowflake issue?

UPDATED WITH ADDITIONAL DETAILS:

I have created a DSN with the details here.  I have made sure that the server url does not have https:// in front of it. 

We are not using an S3 bucket, currently we are just using Snowflakes internal stage.  I have tried with a user stage, table stage and internal stage that I created and then name.  So I have been just slecting my DSN I created, adding the username and password, going to the user stage under local.

I have not touched the alteryx output tool once clicking ok.  

[apathetichell]

can you confirm that you are running with a DSN? are you staging locally? if you are not staging locally do you still have access to your s3 bucket? can you share some screenshots of your configuration settings for your bulk loader and your odbc driver?

[kcampbell91]

@apathetichell - I have updated my original post with some additional details.  I am doing local stage and have created a DSN.  We are not using an S3 bucket.  Thanks for your help!

[apathetichell]

o.k. - next silly question - when you hit test in odbc 64 it works - right?

[apathetichell]

and have you set up an in-db connection and if so - can you datastream in? I guess my other question is when you use your output tool - are you trying to redeclare the database/schema in your output tool - or are you just declaring the table since db and schema are declared directly in odbc 64? and the service account has permission to access the compute warehouse declared in the odbc 64- right?