Building Connections in Designer Cloud
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Printer Friendly Page
on - edited on by randall_king
Please note: progress tracking for this lesson is not available. Please make a note of where you leave off should you need to return to this lesson later.
We welcome your feedback about your learning experience. Please send your comments to academy@alteryx.com.
Hello @randall_king
First of all, thanks for this article. I'm currently exploring the designer cloud and I still have one very important point about data connections.
As you may know, on Alteryx Designer Desktop and classic server, we have two types of data connections :
-in-memory (data is retrieved by the Alteryx machine, processed and then output in the target)
-in-db (data stays in the database, Alteryx just build a query from the workflow design and sends the query to the database)
I asked several times people about Alteryx Cloud Designer and everytime, the answer was : Alteryx Designer Cloud is already in-db. But I still don't understand how you know a connection is in-db or not. From what I see in this article, connections are only in-memory, some with the ability to read data, others with also ability to publish data... but never to mimics the in-database. I must miss something, I think.
Best regards,
Simon
Hi @simonaubert_bd,
In AAC, this capability you’re asking about has been called pushdown. In the future, this will mean that if the following is true:
- data is hosted in a datastore where this is supported
- data is being written back to the same datastore
- additional technical requirements have been met
- The transformation is executed in the database
Hello @randall_king Thanks a lot for the explanations, that was the exact informations I was looking for. I'm impatient to see the in-database released, that will be a killing app :)
Best regards,
Simon