Join the Alteryx Community’s Maveryx Summer Cup event! Compete, network with others, and earn your gold through a series of challenges from July 24th to August 11th. Learn more about the event 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

Loading of ALL the tables in the entire Oracle Database is an overkill in the Input Tool

Hello,

 

I'm using the latest Alteryx Designer version 2021.1. When I drag an Input Tool, before I can proceed with anything, it asks me to choose a pre-saved, named, data connection from the Gallery. This named connection is pre-configured with a USERNAME, target SCHEMA NAME to connect to, with a PASSWORD. This is also known as a PROXY CONNECT method as follows:-

 

USERNAME[SCHEMA_NAME]

 

Once I have selected a named, data connection, the assumption is that in the next screen, if I click on the Tables button, that it would ONLY load the tables inside that target SCHEMA_NAME and not take 10 mins to load thousands of tables that exist in the entire Oracle Database, some of them I would not have access to even connect to, so then why load and make us wait for that long?

 

The same thing should apply WITHOUT a PROXY CONNECT method. For instance, if a saved, data connection only has a USERNAME and PASSWORD, it means the user would like to strictly connect to their own personal schema.

 

Again, when this connection is chosen, the Tables button should strictly ONLY load the tables that exist in this personal schema by the name of that USERNAME and no need to load thousands of tables that exist in the entire Oracle Database.

 

I know the workaround would be to select SQL Editor to open by default which is what I'm currently using but seriously, this has to be fixed as the performance hit and showing of table names for which a user may not even have access to connect to is not good.

2 Comments
AlteryxCommunityTeam
Alteryx Community Team
Alteryx Community Team
Status changed to: Accepting Votes
 
sameerpremji
8 - Asteroid

Just to add to my comment above, Designer should only load the tables for which a user has appropriate grants (SELECT privilege) granted to that user, in addition to the schema objects that the user successfully authenticates into via PROXY CONNECT.

 

Sometimes a user may authenticate into a particular schema, however, they realize that they need a table from another schema which was granted to them by the owner of that schema. As long as there are SELECT grants granted on objects to the user, the user should be able to see them in a list.

 

Oracle provides various VIEWS that do this: USER_TAB_PRIVS_MADE and ALL_TAB_PRIVS_MADE.