May 16, 2012 at 12:38 am
Please help me how I can implement SSIS package security. It includes storage, deployment and execution of SSIS packages. User and type of authentication that is required for connectivity from XYZ (Oracle source) server, destination SQL server and configuration file server/folder.
• Package execution rights: Admin rights to execute batch files that trigger package execution on server.
• Windows authentication: OLEDB connection to SQL server destination database.
• Oracle authentications: TNS service access to connect source XYZ database (XYZ).
Please also suggest some good link for reference.
May 16, 2012 at 1:42 am
Regarding package execution:
it depends where you store the package. I would suggest you store them in SQL Server, so you can levarage SQL Server security. If you execute the packages using SQL Server Agent, you can use the SQL Server Agent roles to secure the jobs.
Regarding the packages themselves:
you need to set the protection level:
Setting the Protection Level of Packages
This will encrypt sensitive or all information in your package.
Note: the only reliable one is SQL Server Storage or DontSaveSensitive, as the other ones can be circumvented. If you do not store sensitive information in your package, you need to bring it in with package configurations. If you store your package configurations in a SQL Server table, you can again leverage SQL Server security.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply