I have a Data Flow task containing several steps. If I break the logic of the flow ie to insert another lookup, the flow starts validating and generates more than a thousand errors in the error list. The most ignoring thing is that it starts counting at 1 error to let's say 1000 and than you see it start counting at 50 and increasing to 1000. Each loop starting at a higher number. All in all this can last for several minutes. All errors are: 'Validation error. <Data Flow Task Name>: The metadata for "input column "" (<ID>)" does not match the metadata for the associated output column.' (The Data Flow Task contains a lot of Union All transformations) I already set the DelayValidation property of the Data Flow and the package to true, but this does not change the behaviour. Is there a way to stop this behaviour?

Can really understand the question but think you want the validation to stop you can do this, select workOffline Abhinav http://bishtabhinav.wordpress.com/

Hi Thanks for your quick response. I don't think I made myself clear. I made a litte example using the AdventureWorks db. It's a simple stupid example showing the insert of the salesorderheader into a datawarehouse table. Just for demonstration purpose, the flow needs to be split into Europe and America. As soon as I delete the arrow between Get Sales Order Header and Lookup RegionCode, the number of errors raises to 159 and as you see the number increasing, you see it get's to 159, starts low again and then get's at 159 again. I just delete the arrow to insert another lookup, so I want to stop this validation. When I reconnect the arrow it's ok to validate again. In my real project the validation of the flow takes several minutes, hanging the visual studio. Setting SSIS to work offline doesn't solve the issue unfortunately. Hope it's more clear now :-)

This behaviour is cz you have moved the input columns out of the metadata as soon as you connect the arrows back and they have same input columns name everything would work out just fine and yes you cant change this behaviour Abhinav http://bishtabhinav.wordpress.com/

Thanks for your response. It's really unfortunate this behaviour cannot be changed. It slows down development intensly. I was hoping there would be a workaround in some way. But Thanks again!

Hi Mr.Midas, If you are using SSIS 2012, the SSIS Designer is smarter about re-mapping columns when a new data source is connected. Columns are re-mapped based on their name and data type rather than by lineage ID. You can more easily resolve issues with disconnected input paths and unmapped columns in an execution tree, by using the Resolve Column Reference Editor. Before version of SSIS 2012, I am afraid you need reference Abhinav's suggestion. Thanks, Eileen TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here. Please remember to mark the replies as answers if they help and unmark them if they provide no help. This can be beneficial to other community members reading the thread.

Hi Eileen, Thanks, the SSIS 2012 is indeed a lot faster. In 2008 it could take for ever. 2012 certainly speeds up things! Midas