Whose account the job runs under?

Question

Whose account the job runs under?

sqlfriend

SSC Guru

Points: 52769
More actions
November 25, 2019 at 8:29 pm

#3700749

I have a sql agent job that is called by a cmd file remotely using an admin account for example I will call it OrchestrorService account.
In SQL agent job history I can see the job was invoked by that account.
But the job step actually is a SSIS package. And the step is run using SQL server service account which is another account.
I tried to figure out the permission issue, both the account is a Sysadmin, I want to know which account it runs under in this case,
the SQL server service account, or whoever invoked the account?

Thanks

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Chris Harshman SSC-Forever Points: 42192 More actions · Answer 1

SSIS steps in SQL Agent will run as the same user that the Windows service "SQL Server Agent" is setup to log on as. If you want to control what account this is, you can setup a credential within SQL Server for the account, setup a proxy in the SQL Agent, and then setup the individual job step that runs SSIS to run as that proxy account:

https://docs.microsoft.com/en-us/sql/ssms/agent/create-a-sql-server-agent-proxy?view=sql-server-ver15

sqlfriend SSC Guru Points: 52769 More actions · Answer 2

The strange thing is that the service account does not have access to a share, but it still can access the file.

sqlfriend SSC Guru Points: 52769 More actions · Answer 3

sqlfriend

SSC Guru

Points: 52769

November 26, 2019 at 9:24 pm

#3701239

Thanks, figured out the access issue

Jeff Moden SSC Guru Points: 1003863 More actions · Answer 4

sqlfriend wrote:

Thanks, figured out the access issue

Two way street here... what was the solution that you figured out?

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Jeff Moden SSC Guru Points: 1003863 More actions · Answer 5

sqlfriend wrote:

Thanks, figured out the access issue

Can you kindly tell us what you figured out? It'll help other folks (and me 😉 ). Thanks.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

sqlfriend SSC Guru Points: 52769 More actions · Answer 6

I found out the account actually does have read access to the directory.

I tested to ask somebody not in our team but in same department to see if she can access it, but actually she should not.

It turns out she can access it.

So I contacted our network admin again to let him know the share permission may not be setup correctly.

He is trying to figure out that.

So it is a share permission issue.