Don't Save Sensitive - update Connection String in Execute Pacage Utility

Question

Hi all,

I am currently studying for the 70-452 exam - and trying to understand 'Don't Save Sensitive' vs. Encryption options.

I have setup a test package with an OLE DB connection using an SQL login.

When I deploy to  my SQL server with Don't Save Sensitive - and open the Execute Package Utility > View Connection String. I can see the connection string with no password.

If I deploy using EncryptSensitiveWithPassword  - the Execute Package Utility prompts me for a password when I click on the Connection String menu, I enter the password, I can see the connection string but still  password is not visible.

Therefore, it appears the password in the connection string is never displayed.

Is this correct? What am I missing?

I have signed up to some practice tests from Transcender - here is one of the questions.

.....

If you want to give Joe access to the package without seeing the password in the connection string

a. Change the protection level to DontSaveSensitive

b. Change the protection level to EncryptAllwithPassword

According to my test - both are correct.

Thanks to anyone still reading.....

Cheers.

Answer 1

Edit of my post doesn't seem to be working....i meant to say:

If I deploy using EncryptSensitiveWithPassword  - the Execute Package Utility prompts me for a password when I click on the Connection String menu, I enter the password, I can see the connection string but still  password is NOT visible.

Answer 2

If you are using windows authentication means.. password will not be visible..

EncryptSensitiveWithPassword and 'Don't Save Sensitive'  are related to package protection levels, if you develop a package and deployed on server with EncryptSensitiveWithPassword the person who knows the password can only open or edit the package..

If you use DontSaveSensitive means some info like password(sensitive) will not decrypted..

Answer 3

thanks for the reply Kingxxx1,

Still confused......as far as I can tell, password is never visibile with integrated Windows Authentication.

Again, am I missing something?

Answer 4

Hi clay123123123,

I agree with Kingxxx1, and you do not miss anything. The Password property is marked as Sensitive in SSIS that means it will not be saved to a configuration file. If you need to save the password, you can save the ConnectionString property to the configuration file, then edit the configuration file in Notepad, and add the password back into the connection string. For more details about Sensitive Data in Packages, please see:
http://msdn.microsoft.com/en-us/library/ms141747.aspx

Please feel free to ask if you have any question.

Thanks,
Eileen

Answer 5

Hi clay123123123,

I agree with Kingxxx1, and you do not miss anything. The Password property is marked as Sensitive in SSIS that means it will not be saved to a configuration file. If you need to save the password, you can save the ConnectionString property to the configuration file, then edit the configuration file in Notepad, and add the password back into the connection string. For more details about Sensitive Data in Packages, please see:
http://msdn.microsoft.com/en-us/library/ms141747.aspx

You can add a configuration of the password of a connection manager to a configuration file. When you create this using the wizard, SSIS will just save an empty string, so you need to fill it in manually after the wizard completes.

@clay: the password is never shown. As easy as that.

---

MCTS, MCITP - Please mark posts as answered where appropriate.