I've got a large Data Flow object with dozens (over 100 each?) of conditional splits, destination objects and derived columns. It's all sourced from a single custom SELECT statement. When I need to break an "early" link in order to adjust the flow, it incurs tens of minutes of "VB is busy" time trying to figure out how many errors there actually are, now that all the downstream objects have no source definition.
In fact, it's still thinking about things as I type this out.
There's something fundamentally sour about waiting for a computer to do something. CPU is at 4%. Memory is fine. Minimal disk activity. How can I tell Visual Studio "Hey pal, I know I'm about to incur some undefined unpleasantries... don't give me too much guff about it.", so that I might keep working?