Tim ffitch (1/21/2016)

---

Koen Verbeeck (1/21/2016)

---

Tim ffitch (1/21/2016)

---

I can see where this would be useful for multiple environments on the same server. When dealing with multiple servers then it would be better to create your environments in Data Tools/Visual Studio using package and project parameters with different values set up for each server. This is one areas where 2012 is so much better than 2008.

I'm not sure how you would specify different values in SSDT for each server?

You mean by using "visual studio configurations"? Like in this article:

https://www.mssqltips.com/sqlservertip/3513/using-visual-studio-configurations-in-sql-server-integration-services-projects/

I still create one environment per server. So scripting the environment would be useful if I add a new server.

Yes exactly that. It makes the management and deployment so much easier. You have to add the parameters into configurations, which is really easy, you can add them all in one go for each package or project at a time. You then have a grid window where you set the values for each configuration. In the deployment set up you set the target server, so when you deploy each server gets its correct configuration, so much easier.