Indication of current server / database in source control pane would be useful
When you select a database in the object explorer tree, then click on the link to existing repository in the red gate source control pane, the highlighted database isn't very obviously highlighted (dependin on your colour scheme) because the object explorer no longer has focus.
In addition, with multiple databases, it may not be obvious which server the selected database is on.
With the link to subversion repository dialog open, it is difficult to check which database is selected - a problem if you have to link a number of databases on a number of servers, and have lost track which one you are up to. Adding the server name to the red-gate pane (along with the DB Name) would avoid this issue.
Similarly, once linked, the DB name is shown in the red-gate pane, but not the server name - so again it is near enough to impossible to see which db (on which server) you're operating with if you have multiple DBs with the same name on different servers.
Ludvig Derning commented
And please disconnect the database choice from the current focused database, when SQL Source Control is slow I would like to continue using the management studio without interrupting the tool.
I agree. I'm shocked this has not been implemented. Please consider adding this feature.
With all of the white space to the left of the database name (upper right) I can't see how this would be more than a 1-2 line change.
Nigel Harris commented
I can't believe this request hasn't been implemented in the last 3 years and 8 months (and counting...)!
The source control window needs an indication of the SQL instance that it is pointing at. As Anonymous commented a mere 2 years ago (nearly), it is very dangerous to be at risk of deploying to the wrong instance.
I commonly have a local SQL DB and a DB on my dev SQL server with the same name - it would be great if the gray text in the upper-right of the Commit Changes, Get Latest, and Setup windows would show the servername of the database that I am currently examining.
Alex Fekken commented
Good point anonymous.
The current status "Good point! Waiting to see if there are any more comments/votes on this..." which was raised "almost 2 years ago" is kind of ridiculous (my opinion): it is an extremely minor change with a maximum of usage since damage could be high if you deploy software not on the system you think you deploy it. Please just add the server-name to the database-name in the sql-source-control panel! Thanks in advance!
Good point! Waiting to see if there are any more comments/votes on this...