+972 52-548-6969
SSISYou really don't need all this data
time to read 1 min | 126 words
Here is SSIS deciding that "No, you really don't need to move this data."
I really like the "smarts" that went into that engine. I make sure that I keep busy and don't move on to othe areas of the application, but dedicate my full an undivided attention to SSIS, as it is apperantly should be.
Would it be too hard to provide a deteministic engine? SSIS would run only (random) parts of the sequence container if I right click it and tell it to "Execute Container". Doing a full debug seems to work, but it execute stuff that I don't want to run right now. Urgh!
More posts in "SSIS" series:
- (27 Jul 2007) The backlash
- (15 Apr 2007) I know better than you do
- (15 Apr 2007) You really don't need all this data
Comments
The pic's not readable. Any chance of a better copy?
It is not readable in purpose, I am afraid.
What it is showing is a completed container with only part of its contained tasks completed.
Ayende,
You can try and disable individual tasks if you want to.
I love SSIS. I mean that completely sarcastically.
Besides the non-deterministic nature of it, one of the other things I love about it is that there seems to be no real way of telling it not to use every single resource on your machine when running.
It was great to have it hammer my dev workstation for 20 minutes, and either succeed, or fail silently.
As Jon pointed out, you can disable tasks within a container, and the SSIS engine will bypass them.
As for hammering away at the machine, there's not much you can do other than limit the size of the caches for lookup tasks (which SSIS does seem to respect).
At the end of the day, you need to have an idea of the size of the datasets that you're dealing with, and tweak the components appropriately (e.g. dumping intermediary data into a db staging table vs staging the data in memory).
Comment preview