We deploy to the SSISDB catalog at a project level using the .ispac file. Then the DBAs use the environment to set up the connections. Is anyone else using this nifty addition to 2012?
SSISDB Catalog? Every day... I find managing environments via the SSISDB catalog to be 1000% easier and more flexible than using config files. Some of the things I'm finding amusing with it are configuring most of the parameters via an environment, and making those default in, then passing in additional parameters via a stored proc call to start up a job.
It made setting up controlled parallel processing of thousands of inbound xml files per hour not only easier, but performance has improved immensely.
For those of you who do this all via the command line. If you need to change the parameters of execution of a package each time its run, and you have enough parameters that may or may not change, how do you get around the 255 character limitation of the CMD prompt? I used to do them via command line execution until I found out that some of my parameters were getting truncated by windows.