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.