SQLServerCentral.com / Integration Services / Data Warehousing / Configuration Table and deployment to Production Server / Latest PostsInstantForum.NET v2.9.0SQLServerCentral.comhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comTue, 31 Mar 2015 15:12:44 GMT20RE: Configuration Table and deployment to Production Serverhttp://www.sqlservercentral.com/Forums/Topic1433072-364-1.aspxHappy to assist. As it played out the configuration file ended up living in the same location in every server in that shop as well but your comment about flexibility is aligned with my view as well. It was an extra option in case that file needed to move, the packages would not need to change. It also gave the developers the ability to store that file anywhere they liked which was important as they may not always have the same drive letters available as the servers.Wed, 20 Mar 2013 13:27:06 GMTOrlando ColamatteoRE: Configuration Table and deployment to Production Serverhttp://www.sqlservercentral.com/Forums/Topic1433072-364-1.aspxHi opc.threeThanks for your useful answer.I did something similar. Just what you said, the only difference is I didn’t create an environment variable to point to the xml file. At the moment I need to store the configuration file in the same location in every server. Tomorrow I’ll implement and document the environment variable. I think it is a flexible and general solution.I will also open another thread to discuss deployment strategies in general. There are a set of new policies and strategies in the company which I work for, and they want to isolate the development team from the production systems. Therefore, the deployment and maintenance should be done by the admins or the operations team.Kind RegardsWed, 20 Mar 2013 12:36:32 GMTPaul HernándezRE: Configuration Table and deployment to Production Serverhttp://www.sqlservercentral.com/Forums/Topic1433072-364-1.aspxA blend worked well for me at one shop where an environment variable pointed to an XML configuration file, and that XML configuration file contained a connection string for a Connection Manager that pointed to my [SSIS Configurations] table. From there the Package Configurations took over and everything was driven by the values in the table, which were obviously different between environments and could be modified via SQL scripts that were deployed into the database at the same time when the SSIS Packages were deployed.Wed, 20 Mar 2013 11:23:06 GMTOrlando ColamatteoConfiguration Table and deployment to Production Serverhttp://www.sqlservercentral.com/Forums/Topic1433072-364-1.aspxHi all,I have to deploy a set of packages from the development server to the test server and later on to the production server.Due to new security policy, developers have no access to the production server, so I have to prepare a deployment strategy.I used package configuration, and it is stored in the SQL Server (DEV Server).In the past I got into the production server, open the package and set the connection to the right SSIS configuration Table manually.I also used other option, is to create the configuration table where the packages are going to be executed, then the address or server name of the configuration table is "." or "(local)"In this way it didn't need to adjust the connection to the server if a move the configuration table, if and only if the packages are stored and are executed in the same server and this server is the default server.I dislike both methods because they are not general and work only under specific conditions.I read something about environment variables but it doesn't convince me.Any other suggestion will be appreciated.Kind Regards,Wed, 20 Mar 2013 03:05:24 GMTPaul Hernández