Alteryx Designer Desktop Ideas

Please add support for Visual Query Builder using Teradata 16. When we upgraded the driver to Teradata 16 from 15 we lost the capability of using the Visual Query Builder in both In-Database and standard connection. Thank you!

When moving external data into the database, the underlying SQL looks like:

CREATE GLOBAL TEMPORARY  TABLE "AYX16020836880b41e08246b59ee8c"

...

My client would like to add a prefix to the table as:

CREATE GLOBAL TEMPORARY  TABLE MMMM999_DM_USER."AYX16020836880b41e08246b59ee8c"

where MMMM999_DM_USER is supplied in the configuration.

A service account  automatically sets the current session to something like MMMM999 (alter session set curent schema=MMMM999;)

Since we can use Snowflake udfs in Alteryx, when do you think Snowflake stored procedures will be available.

A functionality that my team really needs is the ability to use update and delete statements through in database tools. We use Teradata on my team and I'm sure many other platforms also need this functionality. I am really shocked and disappointed that in the update to 2018.4 Alteryx decided that it would add this new functionality to it's Write In DB tool, but only added it for SQL server. Moreover, this functionality is a hole that has been missing in these tools for a long time. Patches in functionality like that need to be added to all platforms, not just one. So please add update functionality to the Write In DB tool for Teradata and other platforms. The original post where Alteryx decided to make only this small change is here: https://community.alteryx.com/t5/Alteryx-Designer-Ideas/In-Database-Update-and-or-Delete/idi-p/13153...

When users execute a sql statement via an input tool, the tool should be smart enough to invoke the (nolock) hint to avoid any database locking when querying a SQL database. Most users aren't advanced enough to understand how to do this in the SQL statement. It should be done automatically or at the very least, a check box option for user.

Greetings,

I am a hands-on guy and work a lot with hana views in SAP space. I have lot of views that are configured with some input variable screens (Filters). Few of these variables are mandatory and some are optional variables. So, that when I try to report off of these views or when I try to do data preview within hana system, a selection screen pops-up and I would enter proper values so that I would get the data that I actually need for my analysis.

From Alteryx, when I connect to Hana (ODBC) and choose my hana view, I am not getting those already configured selection screen variables. I have to reconfigure them within Alteryx to limit my data extract to my needs.

Right now, in my alteryx analytical work flows, to pass the filter values to the  hana view, I am using In-DB tools and multiple Interface Tools (ListBox) to mimic the functionality. 

I wonder, if Alteryx can give me the ability to get the already configured selection screen variables screen (on hana view) into my Alteryx workflow, our task would be much simpler. So that, when I click on magic wand, I would get the pop-up screen similar to the one I would get in my hana system while I do data preview of the hana view.

This feature can be made very useful so that the prompt screens can be embedded in the workflows wherever it makes sense. It doesn't have to be restricted for only In-DB tool pallet. We should be able to include the necessary columns/fields in the prompt screen to accept values. Multiple-Selection, Range, >=, <=, BETWEEN, EQ, <> are some of options for these filters.

If I am not clear, I can explain again.

Thank You,

Suresh Saguturu.

Currently with Alias Manager you can only create Aliases for database connections. 

We use HDFS Connections to write files to HDFS so it would be really useful to use an Alias especially when promoting workflows to Alteryx Server. 

Unlike In-Memory Filter tool, the IN-DB Filter Tool does not process the NULL unless by default specified.

This results in the loss of data without warning.

I suggest you either fix it to match the in-memory filter, or display a warning somewhere, this creates many data quality issues...

NULL entry is NOT included!NULL entry is included

Having an easy selection and filtering of data values is essential in big data environs as well...

I'm sure preparing such an in-db tool for Alteryx guys and gals will be pretty easy...

Looking forward to it...

Background:

Teradata is a high performance database system.  It is highly sensitive to indexes and balancing the records across each index segment.

Teradata uses Spool to perform queries on the database.  It is also very sensitive to type of table (volatile, temp, permanent) created.

Issue:

Alteryx "In - Database" nodes are not providing the ability to configure them to Teradata needs.

As a result, when executing workflows with "In - Database" nodes there is high probability of "out of spool" error specially when working on medium size data base (between 250 million to 1 billion records).

Impact:

Question mark on the ability of Alteryx to handle medium to large databases.

Knime and SSIS are currently preferred to Alteryx

Action Requested

Please change the configuration of the "In - Database" nodes to allow fine tuning of the node behaviour.

Super simple request: Add Exasol to the list of databases that Alteryx can run in-database queries against.

We are using Exasol to store and query large volumes of data (1bn+ rows). This works great from Tableau because not very much data has to leave the database. But when we want to process that data in Alteryx we either have to pre-aggregate the data in Exasol, strip out loads of columns or sit back for hours while Alteryx sucks down the data. The first solution requires somebody to write SQL code in the database, but we are trying to avoid that (that's why we like Alteryx). The second and third are not always viable options.

Given that Exasol is partnered with Tableau, and Alteryx is partnered with Tableau, it feels like there will be lots of Alteryx customers looking for this functionality.

Hello,

I would like to allow my Gallery User to select the fields in my in database workflow, just like we can do in-memory. As of today, it's just impossible to do that.


Best regards,

Simon

The In-Database tools (Connect and/or Data Stream Out) should accept SQL Syntax including comments that use "-", "--", "*/", "\*.   Comments are an important part of SQL code providing documentation and have been part of the syntax for a very long time. 

If there are other syntax omissions they should be added as well.

See attached email thread and Case #00322978

Teradata has a feature called query banding where a group of queries or more commonly a database session can have additional metadata tagged onto all of the individual queries. The Teradata workload management engine can use information provided in the query band for use in prioritizing query execution and resource allocation.

With normal input tools, the query band information can be populated in the "Pre-SQL" with a query such as:

SET QUERY_BAND = 'org=Finance;report=Fin123;' FOR SESSION;

However, with the In-DB tools, there is no concept of pre-SQL, and no great way to set the query band for the In-DB queries Alteryx submits. We would want to set the query band at the workflow level for performance prioritization and resource allocation monitoring purposes. 

Best regards,
Ryan

All the tools in the interface should be populated and assigned/selected with dynamic values.

Now we have the option of populating a set of values for Tree/List/Dropdown.

But we do not have the selecting some of them by default / while its loading.

And Other controls like TextBox/NumericUpDown/CheckBox/RadioButton also should be controlled by values from database.

For example If I have a set of three radio buttons, I should be selecting a radio button based on my database values while the workflow loading.

I think in case we can have a feature at workflow level to check if the entire logic written inside an Alteryx workflow can be converted into a native language, there can be performance improvements in terms of avoiding too and fro between App (here Alteryx) level and DB level.

For e.g. if I am using Oracle as my source connection and target connection as well, and the transformations done in Alteryx can be pushed down to a DML statement (or some loop with commit interval set) to execute within Oracle itself, we might be able to get performance improvements as the overhead of pulling data from Oracle to Alteryx and that of pushing it back from Alteryx to Oracle can be avoided.

What I'd really like to see is In-DB connection with Netezza. Having it available for the input tool is OK but a sore consolation to taking advantage of the speed provided by I

One of the issues I've recently ran into, and discussed with my Customer Success Manager, is Alteryx's inability to natively connect to Snowflake for In-DB Processing using Snowflake's latest ODBC driver versions.

As noted in the Alteryx Help Page below, Alteryx has only been validated to natively support ODBC driver version 2.13.06.00.

https://help.alteryx.com/2018.3/DataSources/Snowflake.htm

As noted per my Alteryx Community ticket below, the Technology Platform team at my company has informed me that they cannot revert our existing Snowflake driver version (Version 2.17.0) to an older version.

https://community.alteryx.com/t5/Alteryx-Designer-Discussions/Snowflake-In-DB-Processing-on-Alteryx-...

As such, when will Snowflake In-DB Connection be compatible with at least the above ODBC driver version?

Thanks,

Alex

I think it would be extremely helpful to have an in-DB Detour so that you could filter a user's information without having to pull it out of DB and then put it back in for more processing.  A time where this would be useful is if you have a large dataset and don't want to pull the entire dataset out of the DB because it will take a long time to pull it.  This would be applicable for filtering a large dataset by a specific state chosen by the user or possibly a region.  The Detour in the developer tools actually seems like it would do the job necessary, it just needs to connect to the In-DB tools.