November 11, 2016 at 12:45 pm
Recently we migrated from SQL 2008 to 2014. I have come across an error that only is happening on the 2014 environment, but working successfully in 2008. Embedded text qualifiers are failing on the new server, but not the old. Has anyone heard if this is a bug on newer environment or any suggestions?
I'm working in SSIS. My Flat File has been defined as using text qualifiers and TextQualifier is set to true on the column. Yet it stills fails for this row.
"test", ""Aubrey" test"
Thank you for any suggestions!
November 11, 2016 at 9:44 pm
Aubrey-314204 (11/11/2016)
Recently we migrated from SQL 2008 to 2014. I have come across an error that only is happening on the 2014 environment, but working successfully in 2008. Embedded text qualifiers are failing on the new server, but not the old. Has anyone heard if this is a bug on newer environment or any suggestions?I'm working in SSIS. My Flat File has been defined as using text qualifiers and TextQualifier is set to true on the column. Yet it stills fails for this row.
"test", ""Aubrey" test"
Thank you for any suggestions!
The problem you have is that the data is not RFC-4180 compliant, as an text qualifier inside the text must be escaped by another text qualifier. Possibly the older instance was more tolerant;-)
😎
This line should be like this
"test","""Aubrey"" test"
x----x,x---------------x
The row below shows the effective text qualified where within, a text qualifier must be escaped by another text qualifier.
November 12, 2016 at 6:18 pm
Aubrey-314204 (11/11/2016)
Recently we migrated from SQL 2008 to 2014. I have come across an error that only is happening on the 2014 environment, but working successfully in 2008. Embedded text qualifiers are failing on the new server, but not the old. Has anyone heard if this is a bug on newer environment or any suggestions?I'm working in SSIS. My Flat File has been defined as using text qualifiers and TextQualifier is set to true on the column. Yet it stills fails for this row.
"test", ""Aubrey" test"
Thank you for any suggestions!
What is the actual failure result? Any error message to go along with the failure?
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply