Is there a way to put in different windows authentication credentials than the one that I am logged under?
I need to be able to be logged out of my domain and still use windows auth using my domain credentials. I can do this in several other db managers, but I can’t figure out how to do this with Toad for SQL Server Freeware
Matt, I think you use another editor in conjunction with Toad-ss, do you have
the capability to login to another domain with different credentials than on
your current desktop system.
As an example my Window 7 Ultimate system is NOT connected to a domain
(userid=Hank_Freeman), but the domain name(userid) I want to log into could be
h_freeman or hfreeman and what I wanted was the ability to specify either of the
later for a specific domain. So I want to put in the Domain name, userid and
password to as to connect Toad.
Lee, Let me know If there is anything, I can do to assist, Currently, I do not
have access to any domain server that has SQL Server, so testing is not
available at this time. I still think this is an idea worthy of your time
Matt, I think you use another editor in conjunction with Toad-ss, do you have
the capability to login to another domain with different credentials than on
your current desktop system.
As an example my Window 7 Ultimate system is NOT connected to a domain
(userid=Hank_Freeman), but the domain name(userid) I want to log into could be
h_freeman or hfreeman and what I wanted was the ability to specify either of the
later for a specific domain. So I want to put in the Domain name, userid and
password to as to connect Toad.
Lee, Let me know If there is anything, I can do to assist, Currently, I do not
have access to any domain server that has SQL Server, so testing is not
available at this time. I still think this is an idea worthy of your time
Hank, I am using SQL Prompt which is a plug in for SSMS not a complete stand
alone tool.
I am not 100% certain but if one were able to select Windows Authentication and
the login and password were not grayed out, and you put
“Domain\UserName” in the user name and put in the password, it
should work as I think there are places where I can put that info in and it
works. But this might not work as MS might have designed SSMS to work like this.
But one cannot do that in Toad or SSMS because when you select Windows
Authentication, the user and password is grayed out.
Just for grins, I selected SQL authentication and tried to put
“Domain\UserName” but that did not work.
Hank, I am using SQL Prompt which is a plug in for SSMS not a complete stand
alone tool.
I am not 100% certain but if one were able to select Windows Authentication and
the login and password were not grayed out, and you put
“Domain\UserName” in the user name and put in the password, it
should work as I think there are places where I can put that info in and it
works. But this might not work as MS might have designed SSMS to work like this.
But one cannot do that in Toad or SSMS because when you select Windows
Authentication, the user and password is grayed out.
Just for grins, I selected SQL authentication and tried to put
“Domain\UserName” but that did not work.
Before you start toad, (in windows 7) you can right click on the toad icon and
do a “Run As Administrator”. From there you can put in any credentials you want.
While that isn’t ideal if you want to run under two sets of credentials for
multiple database servers, it might get you by while Quest addresses the issue.
Before you start toad, (in windows 7) you can right click on the toad icon and
do a “Run As Administrator”. From there you can put in any credentials you want.
While that isn’t ideal if you want to run under two sets of credentials for
multiple database servers, it might get you by while Quest addresses the issue.
Before you start toad, (in windows 7) you can right click on the toad icon and
do a “Run As Administrator”. From there you can put in any credentials you want.
While that isn’t ideal if you want to run under two sets of credentials for
multiple database servers, it might get you by while Quest addresses the issue.
Before you start toad, (in windows 7) you can right click on the toad icon and
do a “Run As Administrator”. From there you can put in any credentials you want.
While that isn’t ideal if you want to run under two sets of credentials for
multiple database servers, it might get you by while Quest addresses the issue.
Before you start toad, (in windows 7) you can right click on the toad icon and
do a “Run As Administrator”. From there you can put in any credentials you want.
While that isn’t ideal if you want to run under two sets of credentials for
multiple database servers, it might get you by while Quest addresses the issue.
Before you start toad, (in windows 7) you can right click on the toad icon and
do a “Run As Administrator”. From there you can put in any credentials you want.
While that isn’t ideal if you want to run under two sets of credentials for
multiple database servers, it might get you by while Quest addresses the issue.
Before you start toad, (in windows 7) you can right click on the toad icon and
do a “Run As Administrator”. From there you can put in any credentials you want.
While that isn’t ideal if you want to run under two sets of credentials for
multiple database servers, it might get you by while Quest addresses the issue.
Before you start toad, (in windows 7) you can right click on the toad icon and
do a “Run As Administrator”. From there you can put in any credentials you want.
While that isn’t ideal if you want to run under two sets of credentials for
multiple database servers, it might get you by while Quest addresses the issue.
I am sorry, I did not get what is suppose to be happening here when YOU run as
Admin… When I change from SQL Server Authentication to Windows
Authentication, I do not want accessible for me put in the domain\userid, which
is currently not working.
Please show me a picture if you have found a way around the issue as described.