Search results for query: *

Paul, I tried splitting them out at one point but may give it another go, I doubt it is the COM object itself as I have .NET app that uses essentially the same call accross multiple threads and it seems to perform well, although in truth I havent benchmarked it. I have tuned the buffers...

Paul, Thanks again for the reply, I tried the union all trick and still am seeing the same thing. The package runs and I get the expected results but I have 68 million records to run through it and at 850 to 900k an hour I feel like I am back to the future and it is 1996 again. But then again...

All processors were used when I took the script task out. Which I find kind of odd since I thought each workflow executed in its own thread.

Thanks Paul, But by default they are set to five I increased this to 10 which is the number of processors +2. Still running predominately on one core.

I have a sequence container in a control flow running on a server with 2 quad core processors and 32 gig of ram. In the sequence container there are 2 dataflow tasks each with a workflow replicated 4 times, incidentally each workflow has a script component that has a reference to a com dll...