In DTS we had an Owner password and User Password. The User pasword allowed someone to run and schedule the package, but not edit the contents. Owner allowed full /designer access.
I like the two levels of password security. What is the equivalent of this in SSIS I can only seem to get ProtectionLevel security to work with a single password that seems to be required to run, deploy and execute. Looks like an all or nothing proposition unless i am missing something.
SSIS Package Security
Cridal
Juergen Wenz
Come on...some one surely knows the answer to this.
Help a brother out.
Zeeshan Gulzar
The single password is just for securing sensitive information, not the package contents. The idea behind the DTS password scheme was to secure sensitive information, but now there are more flexible and just better options I believe, so this is redundant. If you want to use it to protect a package then secure the storage location correctly instead. So no there is nothing like the DTS method.
Chronous
Actually, the single password can be used to secure the package contents..not just sensitive info, use ProtectionLevel "EncryptAllWithPassword". The resulting dtsx package is now encrypted. Viewing the XML is an exercise in futility, and opening the package in VS.NET is not possible, without the password.
Unfortunately you need that same password even just to execute.
What I want to do is allow someone to run the package, but never be able to open it in a viewer to edit. That was the benefit of the User and Owner password in DTS. If you know of another flexible method with SSIS, I'd love to hear it.