Hello Andy,

Well I have made it to the 6th article in your series. Am I correct, that you could set six objects AND change the MaxConcurrentExecutables to 6. Then have each of the 6 objects run their processing on a differnet core? So in effect it is like six sql server 'workers' executing each of the objects?

If I am right, this would be just like having 6 stored proc's that are set to run at the same time (in my case when SAP extracts out all of our files for loading into other databases). So I could create one SSIS package to load all the files into our staging database... and get rid of the stored Proc's... and it would do it simo.. up to the limit of cores + 2, correct?? (Of course the note you have about having the number of objects above the number of cores +2 gives you a random order in execution. So I would have to make sure that nothing was a FK into one of the other tables.)