sql2005| performance adjustment The following attributes can affect parallelism during runtime
1. MaxConcurrentExecutables Properties
This is the property of the package, which defines how many tasks can be run concurrently
A value of-1 means that the number of tasks that can be run simultaneously is the current number of processors plus 2
When Hyper-threading is turned on, it is the number of logical processors
But in one of my little tests, I turned on or off the hyper-threading, and there was no obvious difference (less than 5%), and I'd love to see you have a better view
2. Enginethreads Properties
This is a property of the data Flow task that defines how many worker threads are created when the engine is scheduled
Note that this is a non mandatory attribute, just to hint that the engine can produce so many worker threads, but not necessarily to produce so many
Therefore, when you know in advance that different components may produce deadlocks on the same thread, we can create more threads, such as writing, source data acquisition, and target data acquisition can be in different threads
Of course, some components, such as sorting and merging, may also create their own managed threads at work to handle
3. Maxconcurrent
This is an attribute of the Foreachloop component, which means how many loop instances can run in parallel
From English: http://sqljunkies.com/WebLog/ashvinis/archive/2005/03/29/9825.aspx