Search

SSMS : Add tooltip to "Connect to Server" MRU entries by AaronBertrand

Closed
as Won't Fix Help for as Won't Fix

2
0
Sign in
to vote
Type: Suggestion
ID: 683641
Opened: 8/9/2011 9:25:00 PM
Access Restriction: Public
0
Workaround(s)
This is related to connect #424800. As described in this blog post:

http://blogs.msdn.com/b/sqlrem/archive/2011/07/13/deleting-old-server-names-from-quot-connect-to-server-quot-dialog-in-ssms.aspx

We can now delete entries from the MRU list by using the delete key (or Fn+Delete if, like me, you're using SSMS inside VMWare Fusion).

However, we may have four entries pointing at the same server, and we want to keep the one with the right credentials and/or auth mode, but we can't tell which one it is, since the list only exposes server name. The workaround is to delete all of the duplicates and create a new one from scratch, but this is less than optimal and - with a quick fix - could me made much more direct and predictable.
Details (expand)

Product Language

English

Category

Tools (SSMS, Agent, Profiler, Migration, etc.)

Proposed Solution

Add a tooltip that shows authentication mode, login name (when SQL auth) and - when available and explicitly specified - database name (think contained databases).

If the credentials happen to represent a registered server or cms, the path might me useful information as well.

Primary Benefit

Improved Administration

Other Benefits

Much easier to tidy up this MRU list without using admittedly well-documented hacks.

Virtualization

 
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 10/14/2011 at 2:30 AM

Hello,

Thanks for reporting this issue. We triaged this along with the other bugs for our next major release, but unfortunately it did not meet the bar for fixing. I'm resolving this bug as won't fix for now. However, the DCR suggestion will be kept in our bug DB, and will be revisited the next time we make investment in this feature.

Please feel free to get in touch with me if you have any concerns.

Thanks,
Prashant Choudhari
(prashant.choudhari@microsoft.com)
Sign in to post a workaround.