Hi Phil,

I am using environments for when the project is published to the server (or will be, that is part of what I was setting up).

But when developing a package and debugging/testing I need to execute it from SSDT, obviously. And with dont save sensitive on, I can't even do that unless I hard code the connection string, or add the password to a file manually.

That is the part I'm kind of stuck on. I gather that with prior versions the answer was to create configurations, and that you could have a configuration in design, and different ones in places you deploy to. My understanding was that in 2012 you set up parameters for testing in design, and then mapped them to environments in deployment.

But if the system will neither save nor prompt for sensitive parameters in design, how do you test in design?