Configure an SSIS Package to Execute as a Proxy Account
If an SSIS package needs to execute with specific permissions, you can create a service account for it to use, and the developers can configure the packages to inherit the run as account so that they never need to know what the password is.
Proxies can be used with just about any kind of SQL job step, not just SSIS packages.
8 Steps total
Create a credential under the server-level Security tab by right-clicking on the Credentials node and clicking New Credential...
Enter a name for the Credential, the Windows account you want it to use as Identity, and enter the password for the account twice. Optionally, you can specify which encryption provider to use. Then click OK.
Expand the SQL Server Agent node, right-click on Proxies, and click on New Proxy...
Give the proxy a name, assign it the Credential you created, optionally give it a description, and assign it to the SQL Server Integration Service Package subsystem. You can assign it to other subsystems at this time or any time later if desired.
By default, only sysadmins can assign proxies to job steps. If you want to allow others to assign a proxy, switch to the Principals tab and add their login. Most of the time, you will not do this step in production, but may opt to do so in nonproduction environments.
After pressing enter, the Proxy will show under all specified subsystems. Proxies that have not been assigned, if any, will show under the last tab, Unassigned Proxies.
When creating or modifying a job step for an SSIS package, you can set the Run as account to be a proxy account (default is SQL Server Agent Service Account). The job will only allow you to choose from proxies that were already assigned to the subsystem at the time the job step dialog was opened. If you create a new Proxy while the dialog is open, close it and reopen it to see any new proxies.
Komentar
Posting Komentar
Silakan dikomen...