in theory, you should be able to use this method to share the same user name and password for all the databases you use, but its not perfect. for one thing, you have to use toad security to set this up, and ive not yet figured out how to test it without first creating a database with a password. so you can use this method, but it may not be practical for every dba.
i also had to come up with some recommendationsregarding how to manage your database resources. for example, ive found that there are times when a database may not be of any use to anybody. maybe its a test database that nobody is using, or its a database that is only used for reporting purposes. since the toad software is so widely used in many different companies, its a good idea to make sure that your database resources are not being used by just one or two people. this is where the database resource usage control features of toad come in.
the way to go about this would be to use the configuration manager to limit the amount of memory and/or cpu time that toad users can run up against, while still allowing the applications to run. it really doesnt have to be this complicated. yet as some have requested, its in the works. even if you do go this route, note that you will still need to use the dba module to do the actual control. now some methods you could go about this include:
1. configure the toad browser via application properties to display only the records you want. for instance if you have five or six users, each of them would only see their own records, but nothing else. this way if one user kicks off a fetch of over 2 million rows, say from an oltp system, the other users wouldnt see the negative impact. 3d9ccd7d82