Community Spring Cleaning week is here! Join your fellow Maveryx in digging through your old posts and marking comments on them as solved. Learn more here!
The Product Idea boards have gotten an update to better integrate them within our Product team's idea cycle! However this update does have a few unique behaviors, if you have any questions about them check out our FAQ.

Alteryx Designer Desktop Ideas

Share your Designer Desktop product ideas - we're listening!
Submitting an Idea?

Be sure to review our Idea Submission Guidelines for more information!

Submission Guidelines

In DB : Create View

From Wikipedia :

In a database, a view is the result set of a stored query on the data, which the database users can query just as they would in a persistent database collection object. This pre-established query command is kept in the database dictionary. Unlike ordinary base tables in a relational database, a view does not form part of the physical schema: as a result set, it is a virtual table computed or collated dynamically from data in the database when access to that view is requested. Changes applied to the data in a relevant underlying table are reflected in the data shown in subsequent invocations of the view. In some NoSQL databases, views are the only way to query data.

Views can provide advantages over tables:

    Views can represent a subset of the data contained in a table. Consequently, a view can limit the degree of exposure of the underlying tables to the outer world: a given user may have permission to query the view, while denied access to the rest of the base table.
    Views can join and simplify multiple tables into a single virtual table.
    Views can act as aggregated tables, where the database engine aggregates data (sum, average, etc.) and presents the calculated results as part of the data.
    Views can hide the complexity of data. For example, a view could appear as Sales2000 or Sales2001, transparently partitioning the actual underlying table.
    Views take very little space to store; the database contains only the definition of a view, not a copy of all the data that it presents.
    Depending on the SQL engine used, views can provide extra security.

I would like to create a view instead of a table.

15 Comments
simonaubert_bd
13 - Pulsar

@KylieFHello. This idea has been under review for more than 2 years now. Can we expect an update on this? The in-db functionnalities are the great forgotten of alteryx new features.

Best regards,

Simon

KylieF
Alteryx Community Team
Alteryx Community Team

Hi @simonaubert_bd!

 

Similar to the Pre SQL for InDB idea, this idea unfortunately fell through the cracks due to some Product changes as well as processes involving the idea boards. Our Data Connectors team is actively working through the ideas that fell out of the loop though, and we appreciate your patience while we work through re-evaluating these ideas.

simonaubert_bd
13 - Pulsar

@KylieFThanks for the update. As I see the situation,  for "common" dataprep, there is now Tableau Prep and Alteryx has two main things to play against it : predictive/IA/machine learning  and in-database workflows. As of today, I think Alteryx is pretty mature on the first but not on the second with major issues that could be solved in a very little time (such as this request... writing a create view instead of create table is not that hard 😉 or the one where you can choose the temporary table database/schema).

Best regards,

Simon

simonaubert_bd
13 - Pulsar

Hello @KylieF 

This idea is under review for 4 long years now... it's popular, it's not that complicated to implement  and we have no news, no update for a very long time.

Best regards,

Simon

simonaubert_bd
13 - Pulsar

Hello all,

Just for your information, Dataiku allows the creation of view. That would be nice to reduce the gap with competitors.

Best regards,

 

Simon