Nevyn (11/6/2013)
Thanks for the suggestion, but it appears to still not work.This feature would work for testing different environments in SSDT (for example, a different server name to connect to in a parameter, and you test each server just by changing the active configuration).
But it looks like it has the same overriding issue. Those project configurations are in files, so you can't save a password in them without encrypting, I don't think.
I have noticed that package configurations are still available, so I suppose I could set those up, but I doubt that would be the preferred method. I think we are going to go with "EncryptSensitiveWithPassword" protection. Only downside is all the password prompts, but at least with project deployment it seems to prompt only once per project. We can work around that by organizing our solutions/projects to minimize prompts.
But if any microsoft developers are browsing the forum, a "prompt for sensitive parameters at runtime" option would be awesome to include with project configurations in a future release ....
I'm not sure it's any better, but I just created a one-package project with Don't Save Sensitive as the isolation level.
I then added an OLEDB connection manager with a username / password.
I added a string parameter to the package called password and set 'sensitive' to false for it. I set the value of this to the actual password for the connection - obviously.
I was then able to right-click/parameterise the connection manager and map the $Package:Password parameter to the password property of the connection manager.
I could save and run this.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.