Re: User authentication
- From: William A. J. <WilliamAJ@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 17 Apr 2007 18:58:00 -0700
Hi Sue,
The Windows service account dedicated to run backup inherits the access of
sysadmin, so it is as powerful. So I kind of have 2 options here. If I use
"sa", I have to maintain separate account management. If I use Windows backup
operator account, I have to change login all the time on my workstation to
make changes to backup jobs. So my question is, is there a workaround on the
2nd option? I really want to use Windows backup operator account without
having to change login everytime I access the backup jobs.
Thank you.
William A. J.
"Sue Hoegemeier" wrote:
Okay...so if all you want to do is schedule a backup and then have it.
run under windows authentication and reduce any time managing account,
you may be making it harder than it is.
The owner of the job is a significant factor. If the job is owned by a
sysadmin, the job executes under the security context of the SQL
Server Agent service account. If the job is owned by a non-sysadmin,
it will execute under the security context of the proxy account.
For backups, it's typical and much easier to manage if you just set
the job to be owned by a sysadmin. The job will run under the security
context of the SQL Agent service. You can create the job under
whatever security context you want to log in as - as long as you are a
sysadmin, you can set the job to be owned by a sysadmin account. You
can have the owner be the service account or sa.
-Sue
On Mon, 16 Apr 2007 22:56:02 -0700, William A. J.
<WilliamAJ@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi Sue,
Thanks for the response. What I want to do is configure scheduled backup.
However, if possible, I would like to use Windows authentication as opposed
to SQL authentication. What I have in mind is that it would be easier from
administration point of view this way rather than having separate user
management, Windows and Database.
This is where I am not sure about. If I log on from a workstation and create
a backup job with Windows authentication, it is going to use my account to
run the job. Am I correct? What happen if my account has been removed? Will
the backup still run?
If I have a backup operator account and I want to use it to run the backup
job, I have to log on to my workstation as the backup operator, then create
the backup job in SQL server. Is there a workaround on this? It is a bit of a
hassle having to log out from the workstation and login as the backup
operator to create a backup job.
Thank you in advance.
"Sue Hoegemeier" wrote:
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.
- Follow-Ups:
- Re: User authentication
- From: Sue Hoegemeier
- Re: User authentication
- References:
- Re: User authentication
- From: Sue Hoegemeier
- Re: User authentication
- From: William A. J.
- Re: User authentication
- From: Sue Hoegemeier
- Re: User authentication
- Prev by Date: Re: User authentication
- Next by Date: Re: User authentication
- Previous by thread: Re: User authentication
- Next by thread: Re: User authentication
- Index(es):
Relevant Pages
|
