Re: User authentication



When you chose to use Windows Authentication, generally you
will just be using the windows user account that the person
used to log into the PC or server from where they are
connecting to SQL Server. So if I log into the domain (onto
my PC) at work using SomeWork\Someone then that's the login
that will be passed to SQL Server for authentication. If I
log out and log in again using SomeWork\Another, then
SomeWork\Another is what will be used.
The options are grayed out as the credentials you used when
initially logging onto your PC are the credentials that will
be used.
In terms of the backup task, it's not real clear where you
are viewing the authentication, logins to select. I would
guess it could be you have a maintenance plan and you are
looking at the connections. If you used the wizard, the
selection for authentication is the same thing. It's the
authentication used when they package connects to the
database.
I'm not clear on what you are trying to do with a
maintenance plan and "do the work from my workstation". Are
you trying to schedule this? What do you mean by do the
work? Generally, you'd set up the whatever jobs or
maintenance plans to run on the server itself and schedule
these with SQL Agent jobs. The security context for these is
first determined by the Agent setting, proxies if you are
using those, job owner, etc. The following articles cover
Agent security and proxies:
http://msdn2.microsoft.com/en-us/library/ms190926.aspx
http://msdn2.microsoft.com/en-us/library/ms189064.aspx

-Sue

On Wed, 4 Apr 2007 19:28:44 -0700, William A. J.
<WilliamAJ@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Hi experts!

When using SQL Server Management Studio to connecto SQL Server 2005, we are
given options to connect using Windows authentication or SQL authentication.
My question is, when using Windows authentication, how do we choose to use
other Windows accounts? The login section becomes grey and it automatically
uses Windows account that a user is currently logged on as.

What I want to do is setup a maintenance plan and do the work from my
workstation. When setting up a backup task, it also gives options for me to
use Windows or SQL authentication. Again when I choose Windows
authentication, it does not allow me to pick other accounts. What I already
have is a generic backup account to be used for this purpose.

Could anyone please enlighten me?

Thank you in advance.

William A. J.

.



Relevant Pages

  • Re: Login failed for ServerGuest
    ... | guest and the use of the same account/password does not ... |>I think it is not a limitation in Windows 2000. ... |>use same password for Administrator account on both Win2000 and WinXP ... although Windows Authentication is more secure than ...
    (microsoft.public.sqlserver.connect)
  • Re: Windows Authentication in asp.net 2005 to SQL Server?
    ... If the domains do not trust each other, Windows authentication is not going ... Basic authentication sometimes makes the need for Kerberos delegation go ... generic account to do the backend data stuff on our SQL Server. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: User authentication
    ... With Windows authentication, ... an account is a member of Domain Admins. ... Windows account instead to run backup jobs. ...
    (microsoft.public.sqlserver.clients)
  • Re: Remote connection failed
    ... If you are going over a remote connection or are not logging ... into the domain where SQL Server is then no, Windows ... authentication won't work. ...
    (microsoft.public.sqlserver.connect)
  • Re: User authentication
    ... Server Agent service account. ... What I want to do is configure scheduled backup. ... However, if possible, I would like to use Windows authentication as opposed ...
    (microsoft.public.sqlserver.clients)