On April 3rd, I gave a webinar for Pragmatic Works Training on the Ts on the new SSIS Project Deployment Model introduced with SQL Server 2012. Be sure to check out the recording if you missed the session. If you would like a copy of my slides and code, it is here. Here are the top 5 questions from the session:
Q: How can you deploy just one package if there is a change?
A: In the project deployment model, you can only deploy the project, not individual packages.
Q: When you set up separate configurations within Visual Studio, what happens with those settings when you deploy the project?
A: When building the project, the ISPAC file will reflect the configuration chosen at the time. Under the BIN folder, you’ll find a folder with the configuration name. The default values from the chosen configuration will be seen when deploying from that ispac file.
Q: Does it make sense to have one set of environments for multiple projects?
A: Yes, it does make sense to do that. For example, your production servers will probably be the production servers for many projects. As I mentioned during the session, you will spend some time figuring out how to best use this model in your shop.
Q: Can some packages in a project be in the old model and some in the new model?
A: No, this is set at the project level. It is possible, however, that some of the packages will have parameters and some will not have parameters. This doesn’t mean that the packages without parameters are using the old package model.
Q: What do you do if someone else is supposed to deploy the project?
A: You would just send the ispac file. Everything that you need to deploy the project is in that file.