RE: Non SA Job owner running under SA security context
- From: kirk1880 <kirk1880@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 15 May 2009 05:15:02 -0700
Look in the database security (and I would look at the server security as
well) under the target user and see if it is aliased. The reason that the
user still has the same outcome is because when you removed it from the
server logins the database security may have not changed.
"Jeff Carrington" wrote:
Using SQL Server 2005 SP2, I have a basic job that has one step and.
only runs the following T-SQL:
print 'The user is:'
print suser_sname()
print system_user
The output is as expected for the majority of the logins on the
server, however there is one Windows Auth login that keeps returning
the name of the login that runs the SQL Server agent as if it has SA rights.
This login does NOT have sysadmin rights (or any other server roles) and I
have
dropped and recreated it twice. Has anyone seen this before?
Thanx in advance for any help....
--
Jeff Carrington
DBA
Comscore, Inc.
- Follow-Ups:
- RE: Non SA Job owner running under SA security context
- From: Jeff Carrington
- RE: Non SA Job owner running under SA security context
- References:
- Non SA Job owner running under SA security context
- From: Jeff Carrington
- Non SA Job owner running under SA security context
- Prev by Date: RE: SQLServer 2008 Express + SP1
- Next by Date: Re: Public role not in server role
- Previous by thread: Non SA Job owner running under SA security context
- Next by thread: RE: Non SA Job owner running under SA security context
- Index(es):
Relevant Pages
|
