Home Dashboard Directory Help
Search

SSMS 2008 R2 Login and Password by hmbdtx


Status: 

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


1
0
Sign in
to vote
Type: Suggestion
ID: 742166
Opened: 5/15/2012 7:15:35 AM
Access Restriction: Public
0
Workaround(s)
view

Description

This is how SSMS login is working for me and it does not seem to be correct.

Please follow these steps to reproduce this issue and replace <UserNameONE> and <UserNameTWO> with two of your actual user names.

Delete or rename SqlStudio.bin

Open SSMS and Login for the first time with Login: <UserNameONE> Password: <UserPasswordONE> and check the box to remember password.

Close SSMS.

Open SSMS and notice that the previous login of <UserNameONE> and the password is automatically displayed. This is what I would expect to happen.

Now login for the second time with a different user name and password. Login: <UserNameTWO> Password: <UserPasswordTWO> and check the box to remember password.

Close SSMS.

Now login for the third time with <UserNameONE> information. Login: <UserNameONE> Password: <UserPasswordONE> and check the box to remember password.

Close SSMS.

Now run SSMS again. I would expect to see <UserNameOne> displayed as that was the last user name that had logged in. However I see <UserNameTWO> displayed and this will never change unless you enter a competely new UserName which has not be used before to login to SSMS or delete SQLStudio.bin and start over.

Now no matter what I do each time that I run SSMS <UserNameTWO> will be automatically displayed in the Login box.

Is this the way it is supposed to work?

Details
Sign in to post a comment.
Posted by Microsoft on 1/24/2013 at 7:49 PM
Hi!, thanks for writing in to Microsoft.

We took a look at this bug and triaged it against several others and unfortunately, it did not meet the bar to be fixed. While we are closing this bug 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.