sql windows with different dabase connections

[dvandrade]

Is it possible to have two SQL Windows open simultaneusly connected to different databases (not just different sessions within the same database, but a totally diferent databases)?

 

[aotte]

Not without [ File | New Instance ].

I think there are plans for another approach to this for version 6.

 

[oraclelover]

I think wanting to do that is just based on user prefernce. And if you want to do it you should be able to. I for one have messed up to many times by running sql/pl/sql in the wrong instance in tools like TOAD that have the ability to connect to multiple instances. Try haveing 20 scripts open with some in test, QA, and production instances and after a long day it's easy to make a big boo boo.

 

[aotte]

Agreed, really depends on user and employer differences. Here QA and production only DBA's and a very few select people can do damage, other than eating up machine resources with READ-ONLY queries.

Take your point, I have yet to find that I really need to be able to be logged into multiple instances to do my job properly.

 

[dvandrade]

Thanks for your reply.

I have many different applications (some internally developed, some third-party, some OLTP, some DW), so in my case, it is not development vs QA vs Production, it is more application 1 on SqlWindows 1 and application2 on SqlWindow 2 (totally unrelated tables/objects). So instead of having multiple PL/SQL Develolper "instances", it would be nice to have different SqlWindows connected to differnent databases. Hey, that's why Mozilla "Tab" browsing model rules, as opposed to open-a-new-windows of IE.

I would like to hear from Allround Automation Support if this has been consider as an enhacement.

 

[rbrooker]

i think multiple db connections from the same plsqldev instance would be a good idea. it has my vote.