http://sqlblog.com/blogs/eric_johnson/archive/2010/01/12/understanding-the-ssis-package-protection-level.aspxOne property of all SSIS packages that you must understand is the ProtectionLevel. This property tells SSIS how to handle sensitive information stored within your packages. Most commonly this is a password stored in a connection string. Why is this informationenCommunityServer 2.1 SP2 (Build: 61129.1)http://sqlblog.com/blogs/eric_johnson/archive/2010/01/12/understanding-the-ssis-package-protection-level.aspx#25948Fri, 04 Jun 2010 10:16:06 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:25948Julian<p>Can you provide any further imformation about the ServerStorage option?</p> http://sqlblog.com/blogs/eric_johnson/archive/2010/01/12/understanding-the-ssis-package-protection-level.aspx#45422Mon, 01 Oct 2012 21:36:36 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:45422Brian<p>Nice summary. This has been really helpful. Thanks Eric</p> http://sqlblog.com/blogs/eric_johnson/archive/2010/01/12/understanding-the-ssis-package-protection-level.aspx#47084Wed, 09 Jan 2013 11:52:07 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:47084Phillip<p>Thank you for the information. Now I understand much more about SSIS Package Protection Levels.</p> http://sqlblog.com/blogs/eric_johnson/archive/2010/01/12/understanding-the-ssis-package-protection-level.aspx#48722Mon, 15 Apr 2013 23:24:42 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:48722rupal<p>nice article, curious would this SSIS property setting apply to third party connectors (i.e. Attunity) which appear to not save password to when another user opens/runs the package? I basically, want to persist the passwd regards who opens/runs the job. &nbsp;</p>