Elmo Erasmus
asked on
Execute a SQL Server Agent Job which contains ssis packages
Hi,
Previously I was able to make use of an sysadmin account on our client's server to create jobs and execute packages. The client has now changed the rights of this account so it's not a sysadmin anymore and now the jobs are failing. They don't want to give me another sysadmin account. I now need to know how do I go forward in giving this new account permissions to run Sql Server Agent jobs and to execute packages. The account they have created for me is not a windows login but only a sql login.
Regards
Christian
Previously I was able to make use of an sysadmin account on our client's server to create jobs and execute packages. The client has now changed the rights of this account so it's not a sysadmin anymore and now the jobs are failing. They don't want to give me another sysadmin account. I now need to know how do I go forward in giving this new account permissions to run Sql Server Agent jobs and to execute packages. The account they have created for me is not a windows login but only a sql login.
Regards
Christian
Ask them to edit the jobs and change the user that is executing them to sa.
ASKER
Hi Vitor,
I suggested this to them, but for some reasons they have policies in place which changes the sa account every 2-3weeks. I really don't know why do they do this. Currently the jobs are running on a new sa account, but this will change, according to them.
I suggested this to them, but for some reasons they have policies in place which changes the sa account every 2-3weeks. I really don't know why do they do this. Currently the jobs are running on a new sa account, but this will change, according to them.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Vitor,
In the job steps where I select the type. In this case Sql Service Integration Package, I need to select the package, the package source is SQL Server and then I need to use a user to call this package. They used the sa account and a password for this, but they say this account will expire.
In short, they don't want the sa account to be used anywhere. They want to create an account for me to do this, but they don't know how.
In the job steps where I select the type. In this case Sql Service Integration Package, I need to select the package, the package source is SQL Server and then I need to use a user to call this package. They used the sa account and a password for this, but they say this account will expire.
In short, they don't want the sa account to be used anywhere. They want to create an account for me to do this, but they don't know how.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks I'll have a look at this article and will comment if I require any further assistance.
ASKER
Hi Vitor,
I tried setting up the roles and persmissions as per the article, but when I try to run the package I get this error:
"Non-SysAdmins have been denied permission to run DTS Execution job steps without a proxy account. The step failed."
Is there another way to get this working without creating a proxy account?
I tried setting up the roles and persmissions as per the article, but when I try to run the package I get this error:
"Non-SysAdmins have been denied permission to run DTS Execution job steps without a proxy account. The step failed."
Is there another way to get this working without creating a proxy account?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.