In addition to introducing you to SSIS concepts and components, the article demonstrates how to use those components to develop an SSIS solution that extracts data from a file, transforms the data, and loads it into SQL Server. In such cases, it can help to see examples of how to build SSIS packages that carry out basic ETL operations. Has anybody else come across this type of funkiness or have any ideas about what might be happening ? I'm pretty stumped so any suggestions would be great.SQL Server Integration Services (SSIS) can be a handy tool for developing and implementing extract, transform, and load (ETL) solutions, but getting started with SSIS can seem a daunting task, especially if you’re new to SSIS and ETL concepts. But I am developing an automated process and pulling the data into access first is not an option for me. I do know that another guy in my office was able to get past this by importing the file into access first, then into sql server. I have googled this but cannot find any information on what might be causing this. The missing rows only have 2 fields populated out of the 87 fields in the flat file. I do know from querying the target table that the missing rows are poor quality data. WTF ?!?! SSIS runs this package without any errors or warnings, so POOF my data just disappears. My text file has 633,059 rows but my target table only has 480,212 rows, so I am missing 152,847 rows. So now that my package runs without errors I've realized that a bunch of rows are missing from my target table. This column is a char(1) field but I can live with this workaround.

I suspect it was some end of row funny character or something. I had been getting truncation errors on my last column which is char(1), so I increased the column to varchar(1000) just for giggles. My package just has a flat file source and an ole db destination. I have a very simple package that imports data from a tab delimited text file into a target table.

I only have a small amount of experience with SSIS and I have something very odd happening.

Ssis row is missing in flat file