SSIS package droppping row on import

  • I have a SSIS package which is meant to import 11331 rows into a database table.

    In my execution results, its showing that all the rows are being processed:

    The total number of data rows processed for file "C:\Data\Imports\supp*.txt" is 11331.

    "Suppliers Table" wrote 11330 rows.

    I have unchecked: Column names in the first data row. I can't understand why one row is being dropped.

    Anyone have any ideas?

  • if you ever had the Column Names thing checked, and later unchecked it, I'd replace the component with a new one from the toolbox and make sure to not check that box. ever.

    I have had situations where past status of a component "stuck" despite what its current status showed. Replacing the component has almost always solved the problem.

  • Hi Thanks for your suggestion. I carried that out and I have even developed a new package, however I am still missing the one row on import.Very Strange.

  • Is there a header row that you are counting that does not contain actual data?

    Look at your target table and try to determine if it is the first or last row that is missing, or some row in between. First or last row missing is usually indicative of a problem with the record delimiter in the source file that you will have to code around. If all the data for the missing row crammed into the last column (or other column) on another row you will frequently find a column delimiter in the data. For example if your text file is comma delimited and there is a column with a number that has a thousands separator like 1,589.

  • Totally lost!

    My Header row delimeter is set to: Vertical bar |

    Header rows to skip is 0.

    When i go to the preview the import i can see the top row from my file. I think its some row in between.

    The last show is contained in the table after the import.

  • You need to find out which row it is - possibly by exporting the imported table to Excel and then doing some sort of VLOOKUP comparison - and then work out what is different about the excluded row. I would expect it to be either an unexpected NULL value or an invalid data type.

    If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply