Every time I have to make a change that affects metadata, it's not enough that I update the objects on the target system, then update the SSIS package that points to the system, and then re-deploy the package on the system.
Even though the package will have been updated prior to re-deploy to handle the new metadata, I still have to go onto each system and update the package AGAIN before it will recognize the new metadata. In BIDS 2008, a refresh of metadata on one system would persist to any system it was deployed to.
At this point I'd expect that there would not be a required refresh of the metadata, as the schema of the destination table in UAT matches the one in DEV, to which the package was pointed when it was last refreshed.
Ive created a SQL Server Integration Services (SSIS) project in Visual Studio.To try to address this problem, I added an expression for the Server Name property on the Connection Manager to be determined by System:: Machine Name, thinking that the problem was that changing the Connection Manager on the machine I'm developing on immediately triggered a check of the objects there, even with Delay Validation turned on. I can't find much info about this online, to determine if it's expected behavior with SSDT 2012 or something I'm doing incorrectly or a genuine bug. Honestly, you shouldn't be editing the package to point to another environment before deploying it.Please look into package configurations to learn about methods to deploy your packages without editing the package itself.I dont want to update all my packages manually after theyre deployed to the server.Starting with SQL Server Integration Services 2012, we can use the project deployment model.