Sunday, March 03, 2013 7:52 PM
We're switching over to 2012, and I'm keen to get the logging and reporting benefits of the Project Deployment Model. However, I'd rather not go through the pain of changing all our packages from configurations to parameters at this stage.
I know it's possible to convert packages to the Project Deployment Model, and still have the configuration screen in design model that we're used to seeing in 2008. However, it seems that once they're deployed to the SSISDB, all notion of external configurations goes out the window. I've tried to call the packages on the server from dtexec, which I can do, but the packages retain the variable settings and connection settings that they were saved with i.e. they don't pull in configurations from the external source at runtime.
I've also tried to use the /CONFIGFILE flag with dtexec at runtime, to specify another config file to use, and this just gets ignored.
Can someone please confirm that this is the behaviour of 2012, and that I'll need to switch to parameters if I wish to use the Project Deployment Model.
Monday, March 04, 2013 10:23 AMModerator
Monday, March 04, 2013 10:30 AM
Yep, I've saved my packages like this, and have then done the conversion to the Project Deployment Model.
So far so good.
But when I run them on the server, the configurations are ignored.
Monday, March 04, 2013 10:38 AMModerator
Monday, March 04, 2013 11:41 AM
Yes, they are.