[ https://issues.jboss.org/browse/TEIIDDES-2406?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2406: ---------------------------------------- [~blafond] I am not sure about what you are thinking process with above. So, do not have any comment there. Long time ago, I suggested to create a dummy JNDI connection profile to choose instead of real connection profile to sync up with rest of the framework for situations like this and for Teiid Importer purposes. IMO, Connection profiles has been a some what failed / fragile attempt, as we were doing * Connection Profile (definition) * Connection profile based *local* connection * Data source based on connection profile - preview data source * Data source based on connection profile - *named* a data source * Teiid Importer - Teiid server based connection ( this starts with *named*) * Teiid Importer - Teiid server based connection, connection profile to support the other hooks else where So too many things to keep track of. Teiid Designer does not care for *local* connections except for in the case JDBC importing, rest every thing falls into a server based data source named or otherwise. For that we carry a hefty price of managing these connection profiles and keeping them in sync. So, I have been advocating to remove that hurdle, and base all on the server data source. I know, that is a bigger issue, I may be simplifying the issue, however that is what I would like to see us accomplish. -- This message was sent by Atlassian JIRA (v6.3.11#6341)