0

I've found a SQL Job(s) on a server which run an SSIS package, I've changed the 'run as' drop down to a proxy account which has permissions to run the package. I will change it to my proxy account, run it a few times. However, when I come back to the server after a while and I'll find that it has reverted from my 'proxy account' to the 'SQL Server Agent Service Account'.

Please let me know if you have any suggestions as to why the identity is changing or where to look for clues as I've not seen anything in the logs which indicate that the identity was changed by the system.

jjamesjohnson
  • 639
  • 1
  • 7
  • 11

1 Answers1

2

Is proxy you were using to run SSIS packages is set to default? You can default the proxy to run SSIS package while defining job steps using @proxy_name like - 

EXEC msdb.dbo.sp_add_jobstep @job_id=@jobId, @step_name=N'SSISPackageCall', 
@step_id=1, 
@cmdexec_success_code=0, 
@on_success_action=1, 
@on_success_step_id=0, 
@on_fail_action=2, 
@on_fail_step_id=0, 
@retry_attempts=0, 
@retry_interval=0, 
@os_run_priority=0, @subsystem=N'SSIS', 
@command=N'/FILE "C:\Package.dtsx" /CHECKPOINTING OFF /REPORTING E', 
@database_name=N'master', 
@flags=0, 
@proxy_name = N'SSISProxyDemo';
AgentSQL
  • 2,810
  • 20
  • 22