Search

SQL Server Management Studio Login Box Server name field too short by E4CH

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

1
0
Sign in
to vote
Type: Suggestion
ID: 777743
Opened: 1/29/2013 1:33:19 AM
Access Restriction: Public
0
Workaround(s)
In the Microsoft SQL Server Management Studio 2012 initial "Connect to Server" dialog box, we have to select a server. The last servers are cached somehow and visible when opening the dropdown box. In our company we have server names that are 13 characters long. That's not a lot. But then follows the FQDN (like ".develop.companydomain.net") and then the instance name (in our case USSQLnnMAINDEV or ..UAT). All together, this doesn't fit in the input box. The main information, which server we use is in the last three letters (DEV/UAT/PROD) and that information is not visible. The window cannot be resized and the dropdown doesn't allow edit or scroll. So we have to guess which one is the correct server. See attached screenshot for an example. I've blacked-out some parts of the server names (to not disclose exact server names) in the screenshot, but you get the idea there.
Details (expand)

Product Language

English

Category

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

Proposed Solution

Various solutions are possible:
a) The easiest solution would be to increase the size of the Server name input field by 50%.

b) Making this dialog resizeable would be even better.

c) An even better solution would be a better dialog where you can store (save/unsave) server names with logins etc.

Primary Benefit

Improved Administration

Other Benefits

 

Virtualization

 
File Attachments
File Name Submitted By Submitted On File Size  
SQLselect.png (restricted) 1/29/2013 -
Sign in to post a comment.
Posted by Microsoft on 2/7/2013 at 8:02 PM
Hi!, thanks for writing in to Microsoft and providing this great suggestion.

We took a look at this request recently and triaged it against several others and unfortunately, it did not meet the bar to be fixed. While we are closing this issue as 'won't fix', we have taken note of this internally and we will try & incorporate this request when we revisit this functionality in a future release of SSMS.

Regards,
Sanjay Nagamangalam, SQL Server Manageability
Sign in to post a workaround.