password in the connection
Hello All, I have a problem when type the connection password and reopen the package i have to retype the password , however i checkd that checkbos "Save password" am connection to SQL Server 2008 ... any clue thanks in advance
April 10th, 2011 12:07pm

I'm not sure about what do you mean exactly. But when you create a connection and save the password, this connection will hold password in package. and you can use it everytime. Did you got error in connection while execution? what error?http://www.rad.pasfu.com
Free Windows Admin Tool Kit Click here and download it now
April 10th, 2011 1:35pm

http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/c720e694-2f58-483a-9cd7-3feb7de2db7b . A similar one.Regards and good Wishes, Deepak.
April 10th, 2011 1:57pm

A couple other things to check: check the package protection level (http://msdn.microsoft.com/en-us/library/ms141747.aspx, http://bi-polar23.blogspot.com/2009/04/ssis-and-package-protectionlevel.html). If it is DontSaveSensitive, then passwords won't be stored. If it is the default (EncryptSensitiveWithUserKey) then are you setting the password and setting the "Save password" checkbox as one user and then editing the package as another user.Russel Loski, MCITP Business Intelligence Developer and Database Developer 2008
Free Windows Admin Tool Kit Click here and download it now
April 10th, 2011 1:58pm

A couple other things to check: check the package protection level (http://msdn.microsoft.com/en-us/library/ms141747.aspx, http://bi-polar23.blogspot.com/2009/04/ssis-and-package-protectionlevel.html). If it is DontSaveSensitive, then passwords won't be stored. If it is the default (EncryptSensitiveWithUserKey) then are you setting the password and setting the "Save password" checkbox as one user and then editing the package as another user. Russel Loski, MCITP Business Intelligence Developer and Database Developer 2008 Hi Russ, have checked that solution by changing the protectionlevel to EncryptSensitiveWithpassword but i have to type a password for the whole package however that solve my problem as you described but i don't know if it will wrok when call the package from JOb or i have to do some custome configuration
April 11th, 2011 7:06am

I'm not sure about what do you mean exactly. But when you create a connection and save the password, this connection will hold password in package. and you can use it everytime. Did you got error in connection while execution? what error? http://www.rad.pasfu.com sorry wasn't clear enough,here is the problem when setting the SQL OLEDB connection password and setting the "Save password" checkbox as one user if another user open the package for editing he must retype the connection password again. this problem solved by changing the protection level to EncryptSensitiveWithpassword but i have a concern, what if i schedullad a package is there any custom configuration since the whole packge now has a password after changed the protection level thanks in advance
Free Windows Admin Tool Kit Click here and download it now
April 11th, 2011 7:10am

"when setting the SQL OLEDB connection password and setting the "Save password" checkbox as one user if another user open the package for editing he must retype the connection password again." you should mentioned it earlier. It exactly the ProtectionLevel problem. by default the protectionLevel is EncryptSensitiveWithUserKey, and this means that only the user who are developing the ssis package can see sensitive data ( like password in the connection string ). with changing the protectionLevel to EncryptSensitiveWithPassword, and defining a password, every user needs this password to see sensitive data. if they enter wrong password they can work with package but they should re-setup connections because passwords don't show up. you can see this tutorial on how to set protectionLevel and deploy package and run it as job with EncryptSensitiveWithPassword protection level: http://www.protalk.in/sql-server/steps-to-create-and-deploy-ssis-package-as-a-sqlagent-job/http://www.rad.pasfu.com
April 11th, 2011 7:19am

You will need to edit the Command Line of the SQL Agent job (set all of the other settings first as I believe that once you change the Command Line the other property boxes won't work as expected). You add the following to the command line /De "Password" http://msdn.microsoft.com/en-us/library/ms162810.aspx http://support.microsoft.com/kb/918760Russel Loski, MCITP Business Intelligence Developer and Database Developer 2008
Free Windows Admin Tool Kit Click here and download it now
April 11th, 2011 7:19am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics