Incorrect Truncation Warning in SSIS Data Flow - by Dave Fackler

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 327577 Comments
Status Closed Workarounds
Type Bug Repros 2
Opened 2/7/2008 7:42:29 AM
Access Restriction Public


When a string-based source column in an SSIS data flow is smaller than a destination column being populated via an OLE DB Destination, if the ValidateExternalMetadata property for the OLE DB Destination is set to False, SSIS will incorrectly warn that truncation may occur.  In this situation, SSIS seems to get the metadata for the source column and the destination column mixed up.
Sign in to post a comment.
Posted by DanielBos on 2/8/2011 at 8:39 AM
I still have this problem while using Katmai. Could you guys give it another look?
Posted by Catadmin on 4/16/2008 at 7:57 AM
I have a similar problem with a substring / concatenation issue in SSIS (2005 SQL Server). OLE DB Source & Destination, no middle tasks. I use a CTE to concatenation an AreaCode (varchar 3) to a Telphone (varchar 7) in the following manner:

agyAreaCd + '-' + Substring(agyTelephone,1,3) + '-' + Substring(agyTelephone,4,7) as Phone

This is only 12 characters. I have verified this by putting the same string ina LEN() function in the original query. However, when I put it in my OLE DB Source, the Metadata incorrectly reflects this DT_STR datatype as being a length of 15 instead of 12 and warning me that it may truncate by being put in my destination column of varchar 12.

ValidateExternalMetaData in both Source & Destination is set to TRUE, so it isn't quite the same issue. However, using LTRIM () & RTRIM () around each of my fields & the hypen does NOT resolve the problem. And if I try to change the External Column size at the Source, it complains about truncation at that point. I do not know how to resolve this issue. Please look into this.
Posted by Microsoft on 3/11/2008 at 2:56 PM
Thanks for your feedback. We appreciate it.

We have investigated and fixed this issue. You should try out the upcoming SQL Server 2008 (Katmai) CTP-Refresh build in April/May timeframe to verify whether this issue is fixed or not. Please reactivate this issue if you still hit this problem on Katmai CTP-R build.