Selected DB in SQL editor keeps reverting to systemDSN default

Toad Data Point & Toad Intelligence Central
1

Hello,

After upgrading from Toad Data Point 6.0 to 6.3, I am now facing an issue in the SQL editor when making direct connections to DBs with the native DB user account.

Let's say my NetezzaSQL systemDSN for production is VISUAL_DB for the database field; In Toad 6.0, I would be able to make an IBM Netezza connection in Toad to STG_SMPL_DB using STG_SMPL_DB_USR. Once I opened the SQL editor for that connection, the selected DB at the top would state STG_SMPL_DB...and when I ran any code at all, it would remain the same.

Now, in 6.3 I make the same connection, with the same systemDSN for production, still defined as VISUAL_DB; When I run any code under the connection STG_SMPL_DB using STG_SMPL_DB_USR it will revert the selected DB in the editor to "VISUAL_DB" as defined in the systemDSN.

Is there any way to keep the selected DB from reverting to the DSN defined one in 6.3, or will I need to make multiple systemDSN's to define every single DB connection to avoid that?

2

Hi Jacob,

I've forwarded this to the R&D team to confirm if it is a defect or something changed in the latest TDP version. Stay tuned...

3

Hi Jacob,
Thank you for contacting us.
In TDP 6.3, we implemented database filtration located in connection properties.
From the dropdown menu you can select multiple databases that you want to use, but when using SQL editor you need to manually select the desired db from the dropdown menu.
As a work around you can, as you mentioned, create separate connections.
Hope that this helps you.
For any additional information, we are at your disposal.