SQL code activity enchancement.

[#1]

Right now, SQL code activities are very useful to clean data from the database or modify temporal tables generated in the workflow.

But it would be nice to be able to create temporal tables that can be used in the workflow upstream:

Right now, something like this causes an error, but I would like to be able to do that and generate a temporal table in the workflow that can be followed with other activities.

This would be useful if you need to make complex queries and you want to make the workflow more efficient (not using a lot of activities). It would be useful for beginers in ACC that know a lot of SQL but not so much ACC.

Thank you for reading.

[#2]

This is a great idea for people with a more technical knowledge, we could merge the two worlds: High technical profiles that would prefer to use SQL codes instead of schemas, and less technical profiles that would prefer to use schemas and the activities in Adobe Campaign. 

Anyone knows if this is possible in any way? It would also be useful to visualize data in a more efficient way

[#3]

This concept presents an excellent opportunity to bridge two different realms: individuals with advanced technical expertise who favor SQL codes over schemas, and those with less technical backgrounds who prefer using schemas and Adobe Campaign activities.

Is there any indication whether such integration is feasible? Additionally, optimizing data visualization methods could enhance overall efficiency.

[#4]

Creating temp tables or modifying data in temp tables is not something we support. Not a good practice with any SaaS app/solution. One can certainly query tables with APIs provided or through WF transitions but not temp tables. This feature has been enhanced further with web UI on v8.