How to make sense of IN-DB Sql statements. Reverse Engineer?

[Bpurcell2]

I had a teammate who left the company involuntarily recently.  He had several custom data transformations that are published to our Snowflake instance in views.  I can see the DDL used to create the tables, but it is the IN-DB dynamic output query.  I can tell because the SQL has references like "Tool##_AAA." 

While the views are still intact, some projects need similar data transformations

He stored his Alteryx workflows on an external hard drive and they're gone.  I'm curious if anybody has any tips or programs that can help me rebuild the workflow, simply the SQL to make it easier to interpret or generate some sort of ERDs.

Thanks!

[Warcry]

Super vague please share more details and or workflow screen shots. Please provide examples...

[Bpurcell2]

Definitely not vague if you've ever used IN-DB tools and have viewed at the query output.  Each IN-DB tool generates a SQL statement renaming the output as a "ToolA3_123" type name.  That tool name is used in the from on the next IN-DB tool.

[apathetichell]

@Bpurcell2-> I agree with you - but it is a bit a vague how you're getting the output from dynamic output in-db. You don't have the workflow - correct? I'd really focus on trying to recover the external drive which the workflows were saved on.