Unfortunately, SQL Server is who generates the error and SQL Server does not notify the offending column. This means there is no way for any provider to
get that information.
Evan
--------------------
>Thread-Topic: SQL Server 2005, jdbc error/bug?
>thread-index: AcjSpnp/rv94JfjbTBGajQmLysAQKQ==
>X-WBNR-Posting-Host: 207.46.192.207
>From: =?Utf-8?B?VHJ5IHRoaXMgb25jZQ==?=
>References:
>Subject: RE: SQL Server 2005, jdbc error/bug?
>Date: Fri, 20 Jun 2008 00:23:04 -0700
>Lines: 42
>Message-ID:
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
>Newsgroups: microsoft.public.sqlserver.jdbcdriver
>Path: TK2MSFTNGHUB02.phx.gbl
>Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.jdbcdriver:530
>NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
>X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver
>
>HI,
>
>u mite be exceeding the limit while passing data ra.
>means passing data is more length than field length in DB...
>check it once...
>
>Regards
>kalyani
>
>
>
>
>"Gary at CCB" wrote:
>
>>
>>
>> "Gary at CCB" wrote:
>>
>> > Hi,
>> >
>> > I'm using the latest SQL Server 2005 and jdbc driver. (both downloaded
>> > this week 7/15/05)
>> >
>> > I'm trying to insert xml data into an xml column and am getting this error:
>> > com.microsoft.sqlserver.jdbc.SQLServerException: String or binary data would
>> > be truncated.
>> >
>> > My preliminary testing worked fine. I was trying to load up some production
>> > xml, which is
>> > probably much larger than my original tests.
>> >
>> > Any clues as how to mitigate this?
>> > Are there limits to how large an xml document can be loaded through the jdbc
>> > interface?
>> > Can they be changed/configured?
>>
>>
>> This was not an xml problem at all.
>> It turned out to be overflowing of a different column varchar(64) in the
>> same table.
>> It would be nice if the field to be truncated could be identified in the
>> error message.
>
Evan T. Basalik
This posting is provided “AS IS” with no warranties, and confers no rights.
>> Stay informed about: SQL Server 2005, jdbc error/bug?