Hi,
I have a group of 6 tables I am importing using a DTS package. No particular reason why these 6 are grouped together, except that they all come from the same ODBC connection & DB. The DTS is Create table . . . Copy table sequence for each of the 6. The tables vary in size but the largest is about 14 mb. This is using SQL Server 7.0.
When I tested the DTS by hand, the first 2 tables in the sequence imported OK, then the rest failed. I think it was because the different operations were trying to run concurrently, and got tangled up. I did a new package that specified 'use main thread' and also that didn't start the next table copy until completion of the previous, in the workflow. This runs fine (i.e. brings in all the tables), but it does take a while to run. I am wondering how to structure the package so I take maximum advantage of multi-threading (which I only barely understand), but have it run unattended.
Thanks in advance!
I have a group of 6 tables I am importing using a DTS package. No particular reason why these 6 are grouped together, except that they all come from the same ODBC connection & DB. The DTS is Create table . . . Copy table sequence for each of the 6. The tables vary in size but the largest is about 14 mb. This is using SQL Server 7.0.
When I tested the DTS by hand, the first 2 tables in the sequence imported OK, then the rest failed. I think it was because the different operations were trying to run concurrently, and got tangled up. I did a new package that specified 'use main thread' and also that didn't start the next table copy until completion of the previous, in the workflow. This runs fine (i.e. brings in all the tables), but it does take a while to run. I am wondering how to structure the package so I take maximum advantage of multi-threading (which I only barely understand), but have it run unattended.
Thanks in advance!