It could be as easy as placing a lock to the right of the database name (which shows on the top left for me in SQL Source Control). So once it's "locked" it will not change based on SSMS active object selection (basically the lock disables the code you have currently running on the selection event).

This is a great idea for us too. We are constantly switching databases but each developer like me only has ONE database. It's also frustrating because we are not able to navigate to another database when waiting for the refresh of our own database (and these refreshes are taking way longer than on previous versions).

Drop down would be a good start. It would also help if we could swap servers, too. I have three distinct products with servers located in three distant states, each with their own SVN repository, so changing to a connected server AND database attracts my remaining 1 vote.

I TOTALLY agree with Ludvig's comment about preventing interference with multitasking. SQL Search, SC, SSMS query editors, et al, should all be, as it were, in their own protected environment, if MS makes that possible, of course...

Even better please stop using the last database in the explorer window, since this destroys multitaskiing inside of the Management Studio.
Whenever I do other things while SQL Source is working, I loose the database and have to start over again....

Thank you for otherwise excellent products!

Personally not too bothered, just the ability to select the database would be great. Drop down would be in keeping with SSMS, Alternatively can you link it to the database drop down already in SSMS to handle the linking for the session window?

Interesting idea. Would you want the db name in the upper right to be a drop down, or something that you click on and it opens up your dbs in a hierarcy like format? Any other ideas?