data truncation on varchar(max) column through linked server - by spaghettidba

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.


9
0
Sign in
to vote
ID 811840 Comments
Status Closed Workarounds
Type Bug Repros 4
Opened 12/17/2013 3:34:06 PM
Access Restriction Public

Description

When inserting data through a linked server to a varchar(max) column with a non default collation, data gets truncated randomly at around 30 characters.
The same thing does not happen with:
* non MAX varchars columns
* text columns
* nvarchar(max) columns
Changing the collation of the column to the default database collation fixes.

The repro script uses a loopback linked server, but the same results are returned with a real linked server.

Many collations are affected by the issue. I have a script that tests the behavior with all possible collations: 545 of them fail, 178 work.

I also tested different providers, including OLEDB and SQLNCLI. The same behavior was observed.
Changing the linked server's options that deal with collation does not affect the results.
Sign in to post a comment.
Posted by spaghettidba on 10/15/2014 at 7:43 AM
Why are you closing this as won't fix? Are you saying you don't care about incorrect results?
By the way, nobody ever said it's limited to OLEDB. It doesn't work with SQLNCLI either.
C'mon Microsoft, you can do better.
Posted by Microsoft on 2/18/2014 at 2:20 PM
Dear Customer,

Since OLEDB is deprecated, the only fix for this issue is through Hotfix. Please contact our customer service department to do a further escalation.

Thanks