SSIS 2005 and SSIS 2012 Have Different Data Flow Output

Question

Hi Guys,
I'm currently converting our SSIS 2005 packages to 2012 and I'm finding an odd difference on the Data Flow Output when it imports a txt file to a table.
We have a pipe delimited file ( contains a totals on the bottom row).
CATNO|Title|Total Stk Avail|Stk on Order|Rank|QOH|Allocated|Reserved|BackOrd|WIP|Cleared|Held
CATNUM000067|Fast and Furious|9804|0||9804|0|0|0|0|0|0
CATNUM000068|Frozen|0|0||0|0|0|0|0|0|0
CATNUM000029|Brave|0|0||0|0|0|0|0|0|0
CATNUM000029|Brave with Kinect|0|0||0|0|0|0|0|0|0
CATNUM000029|Big Hero|0|0||0|0|0|0|0|0|0
CATNUM000057|Transformers|27376|0||27376|0|0|0|0|0|0
CATNUM000013|James Bond|121|0||121|0|0|0|0|0|0
,Total Available Stock,524259
And these are the settings for the flat file connection
In SSIS 2005, the total rows are being omitted automatically by the data flow. Basically only 7 rows are inserted whereas in SSIS 2012. 8 rows were inserted including the totals.
if we think about it, SSIS 2012 is correct since we just feed what's ever in the file.
But on the conversion and testing perspective, it's now harder as there's discrepancies between those 2 version.
I just like to check if there's any other discrepancies in terms on results/output between SSIS 2005 and SSIS 2012
Many thanks. 

Answer 1

Hi Vinxster,
After testing the issue that Flat File Connection Manager cannot handle file with total row in my SQL Server 2005 environment, I can reproduce it.
Based on my research, the issue is caused by the Column Delimiter gets first preference and then Row delimiter. This is by design in SQL Server 2005, SQL Server 2008 or SQL Server 2008 R2.
Good news is that the issue is fixed in SQL Server Data Tools which comes with SQL Server 2012. In SQL Server 2012, by default, the Flat File Connection Manager always checks for a row delimiter in unquoted data, and starts a new row when a row delimiter
is found. This enables the connection manager to correctly parse files with rows that are missing column fields.
If you want to fix the issue in SQL Server 2005, there is a sample component posted to the CodePlex that might help you with this:
http://ssisdfs.codeplex.com/
References:
http://blogs.msdn.com/b/dataaccesstechnologies/archive/2013/03/13/flat-file-source-cannot-handle-file-with-uneven-number-of-columns-in-each-row.aspx
https://connect.microsoft.com/SQLServer/feedback/details/293193/ssis-import-of-flat-file-with-uneven-number-of-columns
Thanks,
Katherine Xiong
If you have any feedback on our support, please click
here.
Katherine Xiong
TechNet Community Support