Search
Active

33
Sign in to vote
1
Sign in to vote
Sign in
 to vote
Type: Bug
ID: 282396
Opened: 6/11/2007 1:18:22 PM
Access Restriction: Public
Primary Feedback Item: 281398
3
Workaround(s)
15
User(s) can reproduce this bug
The SSIS natively and with the added components undouble and undoubleout does not recognise embedded column delimiters in text. For example, if " (double quote) is the text delimiter and , (comma ) is the column delimiter the following data :

"Hello ""Hello,Hello"" ","Hello ""Hello,Hello"" "

should be read as two fields : Hello "Hello,Hello" and Hello "Hello,Hello"

How ever, SSIS provided undouble does not recognise the comma in the text content and discards the row. Please fix the undouble to handle this.
Details (expand)
Product Language
English

Version

SQL Server 2005 SP1 - Developer Edition

Category

Tools

Operating System

Win2003 Enterprise Server (SP1)
Operating System Language
US English
Steps to Reproduce

Use SSIS to read the following flat file data (save this line with .csv extension to see how excel correctly hanldes this)

"Hello ""Hello,Hello"" ","Hello ""Hello,Hello"" "
Actual Results
The SSIS flat file connection reads 4 columns instead of 2 columns. Note that undouble and undoubleout generate null rows indicating they cannot read the embedded column delimiters
Expected Results
should be read as two fields : Hello "Hello,Hello" and Hello "Hello,Hello"
Platform
32
File Attachments
0 attachments
Sign in to post a comment.
Posted by toofan on 6/14/2007 at 6:19 AM
Please change category to DTS from Tools.
Posted by djpacman on 6/14/2007 at 12:44 PM
I am experiencing this issue as well. The frustrating thing is that this worked correctly in DTS 2000, but no longer works in SSIS.
Posted by Brent Mills on 6/21/2007 at 3:34 PM
We deal a lot with flat files and this is a huge deal in processing those. The undouble workaround is cumbersome at best. I also have the problem of the flat file writer not writing the proper escape sequences, all it does is wrap the field in double quotes. Can anyone else confirm that?
Posted by Microsoft on 12/3/2007 at 12:42 PM
Thanks for your feedback on this issue. This is an excellent suggestion and we believe that it will certainly make the product easier to use. We have tracked this problem to a more generic issue. We are looking to provide a correction as soon. However, we are not able to include this change in the upcoming Katmai release. I have moved the issue to the next phase so that it will be reviewed at that time. Thanks again for your submission.
Posted by ManServ on 12/3/2007 at 1:35 PM
Defective by design. Microsoft isn't able to fix the main text import driver for 2 releases (SQL 2005 an 2008) that was working before (in SQL 2000 DTS)!?
Posted by Microsoft on 2/20/2008 at 2:08 PM
Even though we are unable to address this for our upcoming Katmai release, we are planning to provide package samples that use script component to parse flat file data that contains column delimiters as text data.

We will update you once these samples are either in a released CTP or are available on CodePlex.com.

Thanks,
SSIS Team
Posted by Microsoft on 2/20/2008 at 3:25 PM
Please use feedback ID 312164 (http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=312164) to trackt latest progress on this feature request.
Posted by Jedak on 7/28/2008 at 11:09 AM
This needs to be fixed. How can you break functionality the worked correctly in a previous version (SQL Server 2000 DTS) and then consider your new product (SSIS) ready for release?!?!? My company uses this and receives files like this all the time.
Posted by ManServ on 8/14/2008 at 3:35 PM
As announced by Microsoft they didn't manage to fix this in the last 3 years with SQL 2008 RTM.
Posted by SetTrend on 8/27/2008 at 4:27 AM
This bug renders the Flat File Connection Manager feature useless. If I have to write my own source/destination filter, then what's the benefit of SSIS anyway??
Posted by ChiefSoftwareArchitect on 6/12/2009 at 11:07 AM
This is absurd. Its still open.
Posted by ajliles on 6/19/2009 at 8:38 AM
This is really a big blunder from microsoft, how can they take such a big backwards step. This kind of import is very common and to have a bug like really makes my life hard, it is very poor.
Posted by ManServ on 8/11/2009 at 11:40 AM
SQL Server 2008 R2 August CTP Flat File Parser still isn't capable of importing RFC 4180 compliant csv files. Also Unicode supplementary characters and line breaks aren't supported with UTF8 files. (Flat File Parser cannot import files with embedded text qualifiers http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=312164)
Posted by A Lockwood on 10/13/2009 at 12:22 PM
Very annoying. Unsurprisingly it's CSV output from *nix systems that SSIS can't import properly. When it's faster to write my own import utility in .NET than use SSIS it just makes me sad.
© 2009 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement