Pre SQL for InDB

Hello,

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,

Simon

Coming Soon

Data Connectors

Category In Database

Comments

danielkresina

I totally agree. The In-DB write table tool should allow pre and post SQL statements to be specified just like you can do with a normal database output or input.

mic_jon

I agree. The In-DB write table tool should have the option to allow pre and post SQL statements.

kirkpoucher

i agree this is a major limitation on the in-db tools

danielkresina

I agree. This request has been out here for over half a year. Can anyone from Alteryx confirm if this concept is in the roadmap? It seems like it should be fairly straightforward to add since it's just another optional SQL command being run before and after the main in-db SQL statement.

MarshallG

aweiss2k

Yes, please add this!!

Thanks.

Any news on this?

+1 Please!

I would love to see this implemented as it would give us the ability to set IDENTITY INSERT OFF and ON which has been a major limitation for us.

alyssa_sedai

This would be incredible helpful to have!

semaj422000

TimN

acowpy

+1 and ditto for Post SQL statements

simonaubert_bd

Well, this is under review for almost two years!!

alyssa_sedai

Hello @simonaubert_bd

It's not. I think they have archived this request as it didn't gain enough transaction.

Although it would be really awesome if this ever got created.

simonaubert_bd

Hello @alyssa_sedai

Why do you think it's not ?

Best regards,

Simon

KylieF

@simonaubert_bd and @alyssa_sedai

Hello!

This idea still is in circulation and hasn't been archived. Due to product management and process shifts some ideas unfortunately fell through the cracks, including this one. However we're actively working to get these ideas re-evaluated by the current product team and updated with a more current status. We appreciate your patience while we address these ideas and hope to have a more up to date response to you in the near future.

alyssa_sedai

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.

mscuaycong

@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.

simonaubert_bd

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,

Simon

mscuaycong

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

alyssa_sedai

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.

Benjamin_Schalk

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...

alexnajm

Especially needed for the IDENTITY_INSERT ON and OFF

steven4320555

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.

jineshnp31

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.

Thanks!

dchu

Any updates on PreSQL statements within the InDB tools?