Sometimes if a session is hung on the database, I can kill the session, that will free it up. Sometimes its not the session, I might be creating a table, kill session on the database, TOAD still hung. Have to kill the app. grrr when this happens. Im finding the frequency of this so bad its becoming a real hindrance to work.
I had thought TOAD had gone multi-threaded several years ago so if a session is hung, you can still work on other sessions? am I wrong on that? if I am, why isnt it multithreaded? SQL server management studio good example of a DB gui, not hanging round waiting on a session to come back