SqlDbx
You are not logged in.
Pages: 1
I frequently run two or three SQLDbx instances side by side (yes, I am a Professional version subscriber!). For instance, I'm working in one database, but need to see objects from another database simultaneously (and in it's own monitor on a multi-monitor setup). It would be great if SQLDbx would save each session's scripts individually upon close. You could do this for as many instances are opened up. If I then open up my three instances, they each would be setup with their previous environment....cool.
The complication here (but maybe not complicated for you!) lies in the desire that the sessions need to be numbered in the REVERSE order in which they are CLOSED. Say I open up Session1, Session2, and Session3. Then I close Session 2, then close Session 1, then close Session 3. Since Session 3 was the LAST one closed, it should be the Session3 that is restored the next time I open up SQLDbx. If I open another SQLDbx, then Session2 should be restored. If I open yet another, then the original Session1 should be restored. If this is all too difficult to handle accomplish, then just allow saving of 2 Sessions.
No other DMBS client does this...let's be the first!!
Thx,
Allen
Offline
SqlDbx already supports multiple sessions. The only issue right now that when you exit SqlDbx it saves state to a default workspace and not to the currently open. Also on startup it opens default workspace and not the one last used.
Offline
Yes, SQLDbx supports running multiple sessions of SQLDbx, but not saving/restoring multiple sessions. So how about putting the session workspaces in a stack, and restoring in reverse order (last one used opened first, 2nd to last one used opened second, etc...)?
Offline
Pages: 1