Oh no! The Community appears to be haunted! Help us find all the spooky specters here.
We are currently experiencing an issue with Email verification at this time and working towards a solution. Should you encounter this issue, please click on the "Send Verification Button" a second time and the request should go through. If the issue still persists for you, please email support@alteryx.com for assistance.

Alteryx Designer Ideas

Share your Designer product ideas - we're listening!
Submitting an Idea?

Be sure to review our Idea Submission Guidelines for more information!

Submission Guidelines

Pre SQL for InDB



We use the pre-sql statement of the input to set some parameters of connections. Sadly, we cannot do that in a in-db workflow. This would be a total game-changing feature for us.


Best Regards,



8 - Asteroid

Hello @KylieF,


That actually really good to know! The fact that we don't have the ability to do PreSQL is increasingly a problem and forcing us to consider other tools.

7 - Meteor

@KylieF  there is a workaround that might help...  

At our company, we have data in Hadoop queried via Hive or Impala.  I use Indb tools for efficiency but some of the tables in the data schemas in Hadoop need to be REFRESHED by issuing a SQL command, prior to the queries being run.  Since, the Indb tools don't have this pre-sql option, I use the input data tool first to run the refresh table in Pre-sql and then run the indb tools.  This way, I don't have to manually intervene and can schedule the full workflow.


Use the Input Data tool  (Pre-SQL is only available here at this time) just to run your pre-sql code.  Then, you can switch to the Indb tools to run your queries.  I suppose depending on how complex your pre-sql code is... this might work.  See figure below.




Hope this helps.

11 - Bolide

Hello @KylieF Good to know, thanks for the update.

@mscuaycong  I usually use pre-sql to pass set instruction linked to session, such as container size or queue in Hive. This won't work if I use a input tool because it will be two different sessions.

Best regards,


7 - Meteor

oh, too bad... @simonaubert_bd ... let's keep pushing for the ability to have pre-sql statements in the indb tools!!



8 - Asteroid

Hello @mscuaycong and @saubert,


Thank you both.  We have tried using that workaround and it works for some things but as @saubert pointed out it doesn't work for everything. It is truly an issue that we don't have a pre-SQL tool.

7 - Meteor

Having Pre-SQL for In-DB would be especially useful for connections to e. g. Snowflake, where you can use different warehouses to access different compute resources. 

This links directly to the amount of money you pay while working / developing.

Right now the only workaround I see here would be to have different connections set up and choose the one you need, but that's annoying if you have a lot of options...

8 - Asteroid



Especially needed for the IDENTITY_INSERT ON and OFF

8 - Asteroid

Functionalities like this is hugely beneficial, especially, when working with large datasets or centrally managed databases. Is there a roadmap for Alteryx's in-DB capability? What are the priorities?


I guess this idea is less database dependent, and once implemented, can benefit a lot of use cases. 

8 - Asteroid



Will be very helpful for even simple things like adding presql scripts to set query tags on Snowflake for which, only indb tools work best.

This makes a massive impact on how we can analyze the utilization of Snowflake by different teams/applications based on query tags.


Would love to see presql for indb tools.