MSFT: EDW - TAPBLOCK - BCP doesn't recognize | field terminator on code page 65001 - by Sergey Galuzo

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


7
0
Sign in
to vote
ID 321839 Comments
Status Closed Workarounds
Type Bug Repros 4
Opened 1/10/2008 2:19:09 PM
Access Restriction Public

Description

BCP fails to recognize | field terminator in certain cases with code page 65001. This leads either to data corruption (data from more than one file field lands in one column) or to row rejection due to field/column misalignment. 

In the same conditions BULK INSERT imports data correctly. Unfortunately BULK INSERT cannot be used in all the cases (double-hop).

Also we noticed that BCP does not work well with format files when code page 65001 is used. We hope that this can be fixed together with the main problem above.
Sign in to post a comment.
Posted by Matija Lah on 9/29/2008 at 1:20 AM
That sounds like a very honest explanation. Perhaps too honest? ;)
Posted by schmalzdackel on 9/25/2008 at 8:50 AM
sh0k!
Posted by Microsoft on 1/21/2008 at 4:18 PM
EDW Team,

SQL Dev has completed our investigation into the fix for this issue. Our estimate is: 3 weeks/dev and 4 weeks/test for Engine and the same for Client. To do this work, we would have to abort other DCRs/bug fixes currently planned which will directly impact the quality of Katmai.

While we would like to help you out, we believe the cost of this effort is too high and we have decided not to fix it. The solution is to build your own converter prior to loading the UTF-8 data into SQL Server. We are eager to provide UTF-8 support in a future release of SQL Server; hopefully as soon as SQL11. With that in mind, please be sure to make this conversion process separate enough to your application that you can easily remove it in the future.

If require us to re-evaluate our decision, please re-escalate this issue through Alexey and me.

Thank you again for your contributions to SQL Server. We all wish we could fix this for you without compromising the quality of Katmai.

Sincerely, Maria Balsamo
SQL Server Development Team
Posted by Debra [MSFT] on 1/11/2008 at 9:11 AM
Thank you very much for reporting this issue. We are investigating now and will get back with you shortly with more information.