SSIS Import of flat file with uneven number of columns - by Cozumelk

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 293193 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 8/14/2007 7:20:56 AM
Access Restriction Public


SQL Server 2000 SP4 successfully imports over 30 comma delimited files a day.  The rows in the files vary in width.    A carriage return and line feed is the end of row indicator.  SQLServer 2005 SP2 will not correctly import the same files.  SQLServer 2005 ignores the end of row indicator.  When a row follows a row with fewer columns, the row is pulled in at the end of the previous row.  Since SQLServer 2005 doesn't see this as an error, the records aren't written to an error file.  The import just turns up several thousand records short.  Changing the files is not an option.  This must be a bug because SSIS allows the end of row indicator for a file to be selected during development.  This problem may cause us to abandon plans to upgrade to SQLServer 2005.  Any work around will need to be efficient as other jobs rely on this data.
Sign in to post a comment.
Posted by Jing [MSFT] on 8/11/2010 at 10:29 AM
Thanks for reporting this issue. The fix will be available in the next major release of SQL Server Integration Services.
Posted by Microsoft on 3/25/2010 at 12:43 PM
This is fixed for an upcoming major release of SQL Server. Specifically, delimited files containing rows with differing numbers of fields are parsed properly.
Posted by Microsoft on 9/9/2008 at 11:21 AM
Hi Cozumelk,

there is a sample component recently posted to the CodePlex that might help you with this.

The component name is Delimited File Reader and it can be found here:

The sample component can parse rows with missing fields and embedded qualifiers.

Bob Bojanic