All 200+ packages use a single .config. I have used notepad to change the SERVER NAME in both of the Connection Managers to the Test environments. Same user and PW are in place. When I open a package from source safe I have to reset the config file to the package, because it was pointing to the PROD environments, it will make another open package revert back to unsaved via that 8 in the title. Why would a tweak of the config effect other packages? because "All 200+ packages use a single .config."Arthur My Blog

This is a real DW experience that I am porting to a test server for a repoint of all incoming data from our new ERP upgrade. As a .NET programmer I know to set the new values in the config file and every package will read the tweak and point to the new location, just as all of my .cs code does. Sorry by no that doesn't happen at all now does it? OK I'll reset this package to re examine the config file through the SSIS | Package Configurations wizard. But that process wants to just REWRITE the config file. Sorry but I am in control not you stupid little wizard. I set the .config to be read only and repeat the wizard process now it seems to accept MY tweak and not plow over the file with all that other crud. Can someone answer me how you would do this for 200+ packages? That is what a config file is all about to allow an administrator to make an edit as needed without bringing in developers, or did I miss that point? Now how do I populate a new SSIS server with all of these packages? I don't trust the deploy option to be honest with you because it was used to populate the current SSIS server. I fell 75% certain that it will overwrite my production system with everything I want to place on the test system. Is there a better way that I am not aware of or do I just shut up and grunt it out one package at a time? TIA If interested I'll make a video to show what is going on. I have 190+ packages still to go!

Sounds like you are doing something wrong and from your description it is hard to decide what that is. If you have an existing config file, you can just edit it. If you are saying that your package does not use the config file then you are not passing the config to the package either in the job or via dtexec. As for deployment - I generally do that manually in a production environment. You don't mention if you are using SQL or file system storage.Chuck

Once the Package Configurations wizard creates the package config file it can be modified manually after, but only the parameter values must be modified. And this can be done using any text editor. The file should not be set to read only, but it is OK to make it so after the package is deployed. To re-use the same config file across packages you can just instruct the Package Configurations wizard to use an existing config file (an option at the bottom). Arthur My Blog

Hi, You are a .NET programmer? Abandon hope all ye who enter here (Dante) If I understand you well, the 200 packages have configuration files, you want to further develop on these packages on your development machine, but use copies of the configuration files that point to test servers rather than production servers. You have to change each package to use another location for the config file (your version of the config file). In the long term I would suggest tostart using system environment variables on your development machine and on the production server. Had those packages been designed like that, all you would have needed to do is create the system environment variables on your development machine. But you will have to bite the bullet and go through the process of reassigning these packages that way. Jan D'Hondt - Database and .NET development

All 200+ packages use a single .config. I have used notepad to change the SERVER NAME in both of the Connection Managers to the Test environments. Same user and PW are in place. When I open a package from source safe I have to reset the config file to the package, because it was pointing to the PROD environments, it will make another open package revert back to unsaved via that 8 in the title. Why would a tweak of the config effect other packages?

All 200+ packages use a single .config. I have used notepad to change the SERVER NAME in both of the Connection Managers to the Test environments. Same user and PW are in place. When I open a package from source safe I have to reset the config file to the package, because it was pointing to the PROD environments, it will make another open package revert back to unsaved via that 8 in the title. Why would a tweak of the config effect other packages? because "All 200+ packages use a single .config."Arthur My Blog