Set up an execution account when the SQL Agent runs the job

Anyone who's ever used SQL Server should know that using SQL Agent can build some automated jobs to help us periodically perform some tasks, where executing an SSIS package is one of those tasks. Some localized operations, such as reading files, are sometimes performed in SSIS packages, and if the Execute account permissions for the Execute SQL Agent task are insufficient, it is possible that the SSIS package cannot read the file execution failure. So we sometimes need to specify which account to use to execute the SQL Agent task.

1. To specify the execution account for the SQL Agent task first create a database credential, as shown in:

2. The identity selected when establishing the voucher (the account specified in the Red box) is the execution account behind the SQL Agent task.

3. Then create a proxy role for the SQL Agent

4. Remember the name of the credential when you set up the proxy role Select the credentials that we created above (the first red box), and then in "the following sub-systems are valid," Choose the SQL Agent task type that the agent role will use, in this case we select the task type is the SSIS package (the second red box).

5, and then when the SQL Agent task is established, if you choose the task type is to execute the SSIS package (the first red box), you can select in the run identity of the agent role we established in the previous step (the second red box), to use the identity account specified in the 2nd step of this article to execute the SSIS package

Set up an execution account when the SQL Agent runs the job