I am trying to see how I could help translate a particular Alteryx workflow that I created into a SQL query that could be run by the client in the future since they don’t have Alteryx. My knowledge of what that would take or even the questions to ask is very low. I know in Alteryx there are “in-DB” tools that I guess are coded in SQL language? But I pretty much no nothing about SQL queries. Anyone know what the process would look like to convert what I have created in Alteryx into SQL language that I could then handover to a client so they would be able to utilize the workflow logic in the future? Any help would be greatly appreciated.
if this in-db -dynamic output in-db and then choose the SQL query as the output.
Do each of my tools (I.e., formula in DB and filter in DB) need to be in SQL language or do I use standard alteryx language?
Hi -
This is going to largely depend on the complexity of the workflow and which database you are connecting to. If the workflow has “many” tools (in quotes because can’t easily define it), it will be more difficult as the number increases. Database also makes a difference as different databases have different toolsets.
Seems a bit odd that a (presumably) client deliverable was developed with a tool that the client doesn’t have.
Can you sure more details, such as backend database, and at least a screenshot of the workflow?
Mark
tell the client to buy Alteyrx.
^this
This won't be a trivial task, even if the workflow is the simplest possible, i.e. select from a table and create a file. Unless the output file is a simple txt/csv file, what tool will you use to create, say, an Excel file? Is there anybody on your team that is knowledgeable of SQL?
Is it impossible? Absolutely not; I've been working with SQL databases for 30+ years and only just started using Alteryx 18 months ago. Just don't be under the impression that you can simply save a workflow as a "SQL program".
Mark