Search

SSMS - Allow login with other domain and user by ben.st

Closed

5
0
Sign in
 to vote
Type: Suggestion
ID: 774357
Opened: 12/14/2012 5:25:44 AM
Access Restriction: Public
0
Workaround(s)
There are legitimate times that a DBA would want to connect to a SQL instance that resides on a different domain from that of their workstation where they are running SSMS. At present, SSMS fills in the user with the currently logged on Windows account for Windows authentication, but does not allow the end-user to change or input a different user.

Although it is possible to use the runas command under certain circumstances, this is not the easiest of solutions and the behaviour of SSMS is to still display the workstation Windows account in the string in Object Explorer (SQLServer (SQL Server xx.x.xxxx - WorkstationDomain\WorkstationUser) ) rather than the user used in the 'runas' command.

It would be beneficial if the DBA were not blocked from entering different user credentials into the login dialogue of SSMS.
Details (expand)

Product Language

English

Category

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

Proposed Solution

Allow user to modify the user name when connecting to database engine by SSMS.

Primary Benefit

Improved User Interface

Other Benefits

Would allow a DBA to manage multiple and disparate domains from one workstation.

Virtualization

 
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 2/5/2013 at 5:10 PM
Hi!, thanks for writing in to Microsoft.

We took a look at this feature request 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.

As you noted, a reasonable workaround is to launch SSMS with runas. And you can also use the "/netonly" switch for the runas command to log in using remote credentials on a domain that you’re not currently a member of, even if there's no trust set up.
Example: runas /netonly /user:domain\username <program.exe>

Regards,
Sanjay Nagamangalam, SQL Server Manageability
Posted by SAinCA on 12/18/2012 at 3:01 PM
With FOUR Domains to contend with and only 1 Windows credential possible, all the tools I have locally are useless if I must login via RDP onto the distant domain server.

Please give us this ability, Microsoft. Other tools do...
Sign in to post a workaround.
© 2013 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement