Okay, I've had another go, setting up a series of Tasks, one for each table and setting the maximum number of Parallel jobs. My problem now is that I want the job to be re-runnable - i.e. I need the facility to set the job going again to transfer only the tables that didn't transfer the first time.
I have tried setting the 'Enable Step' Workflow property to no, but then any Tasks that need to run after the main data copy over will not run because of the Tasks that didn't complete.
I've tried to show this in the following diagram:
Transfer Table 1 Transfer Table 2 Transfer Table 3
| (Transfer) | (Disable) | (Transfer)
Perform further Processing
As the Disabled job (Transfer Table 2) has a Completion Workflow arrow, it must complete before the next stage can take place - it will not complete as it is disabled!
I think I'm starting to see things now, so I'm going home for a lie down.
Any assistance would be very gratefully received.
I am considering trying Bulk Insert in a TSQL Stored Proc although I would need to use bcp to get the data out from the 6.5 system and work hard to get a Parallel import - but it may be worth it!