Adding 1 destination column causes DTS to fail.

[PhilEngle]

I have the developer edition of SQL Server 2000. I also have a DTS package that imports from a text file into a SQL Server 2000 database table using the standard OLE DB provider for SQL Server supplied with DTS. It worked fine UNTIL I added ONE column to my destination list in order to import further columns from my source text file. The resulting package TESTed fine while outputting to the TEST text file. However, when I actually ran the package zero-or-one row was imported, rather than the 50 or so rows I expected.

Note that it doesn't matter WHAT column I add to the selected destination list: ANY such added column causes import failure. (Also, this occurs even if the ActiveX code for my multi-phase data pump is unaltered.

Any idea what's going on here?

 

[Meleagant]

Did you try and redo the mapping under the Transformation tab of the pump task? Sometimes SQL gets picky if a table has changed and you don't go back into the DTS package open up the pump task, double check that the destination is accurate in the drop down box and then click on the transformation tab. My best guess at first glance.

Journeyman -- The Order of the Seekers of Truth and Penitence