Quantcast
Channel: SQL Server Integration Services forum
Viewing all articles
Browse latest Browse all 24688

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

$
0
0

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.




Viewing all articles
Browse latest Browse all 24688

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>