June 3, 2011 at 11:31 am
Hello,
I have a job which is working fine under my personal window domain account, now I need to let the job running under a special group account, where my id is included there, and ids of other people. How do I do this?
Thank you very much.
June 3, 2011 at 11:53 am
Can't, a group can't own a job or package. It's been driving me nuts for developers for years when I don't want to give them overkill rights.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
June 3, 2011 at 12:19 pm
That group needs to be added to the local sever you are trying to run the job on. Have you confirmed that..? For instance when I setup replication I have a AD account that talks to both servers, and both servers use that login for the jobs, that login was added to the server.
The other thing it could be is the SqlServer Agent (service) needs to run under that name you want to use, from what I recall you can't have the agent run under one login, and have one job use a different account, its all or nothing. I think the concept of RunAs was enabled in 2008 to solve that issue, but in 05 its not that way.
I would check, and or change the login credentials the Sql-AGent is using to this account so all jobs use that login.
June 3, 2011 at 12:24 pm
What I just figured out a work around is: (and it is working)
Configure the job running under a dedicated proxy with a credential created from the dedicated account (not the group)
Thanks all
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply