Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SSIS - Truncation Warnings


SSIS - Truncation Warnings

Author
Message
parody
parody
SSC Rookie
SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)

Group: General Forum Members
Points: 32 Visits: 293
absolutely, the issue wasnt so much how to do it, but how to automat it for 1000 + columns. Not something anyone wants to do one by one.

In the end I generated a dynamic insert statement form system tables to insert one row maxing out all data lengths (all varchar), exported it and used it as a dummy fikle to autop detect. Bit of a pain but not as bad as the alternative!

What would have been ideal is to be able to automatically use the target tables dt's as the source dt's. The table was built from the file spec so they are identical max lengths.
ThomasRushton
ThomasRushton
SSCommitted
SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)

Group: Moderators
Points: 1823 Visits: 2179
Hurrah! This has solved a problem that's been bugging me for a few days. Thanks!
girish.khullar
girish.khullar
SSC Veteran
SSC Veteran (230 reputation)SSC Veteran (230 reputation)SSC Veteran (230 reputation)SSC Veteran (230 reputation)SSC Veteran (230 reputation)SSC Veteran (230 reputation)SSC Veteran (230 reputation)SSC Veteran (230 reputation)

Group: General Forum Members
Points: 230 Visits: 17
This problem occurs while using the data transformations.
SOLUTION
You need to check the length of the attribute should be same at the database as you are setting in the transformation.
vionex
vionex
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 230
Something strange... i don't think that this problem is in data transformation. In my project i have only source->destination component and same warnings(source external/output and destination input column lengths are the same(as actual table value), but destination external column length is smaller).. And solution to go through all column list and edit their length is... not optimal for large structures.
ppgarza
ppgarza
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 2
[qu:-D:-D:-D:-D:-Dote]ammumariamphilip (6/28/2010)
Hello All

Truncation may occur due to inserting data from data flow column "column_name" with a length of 77 to database column "column_name" with a length of 7."

To resolve this, I had to:

open the Data Flow task
From the source task right click and select
open Advanced Editor.
go to Input and Output Properties tab
expand OLE DB Source Output
Expand External columns and check the specific columns
which give the error and the corresponding length.
This length should ideally be the lenght of the column as designed in your database table.
Now Expand Output Columns
click on corresponding column which gives the error and you vcan notice that the length value won't be the same as that in your external column or your database design .
change Length property of the column to that of the actual table design length and refresh .


I also went to target side:

open Advanced Editor (on OLE DB Destination)
go to Input and Output Properties tab
Click on Refresh button
and also ensure to check the value of the length is reflecting correctly.

The truncation warnings vanished immedaitely Smile[/quote]:-D
SZARS
SZARS
Forum Newbie
Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)

Group: General Forum Members
Points: 9 Visits: 76
I applied this solution but it keeps on changing the warning from souce to destination and back and forth.

Here is my issue and it just keep on torturing me.

My source is CSV and I have one column that has length of 50
My destination is OLE DB, and there; that column's length is 15

I have to set the error as ignore and process shows Green but table is empty.

I set the coulm to 15 at source (csv) and warning switches from destination to Source

I do the refresh and warning comes back to destination
Paul Hernández
Paul Hernández
SSC-Enthusiastic
SSC-Enthusiastic (173 reputation)SSC-Enthusiastic (173 reputation)SSC-Enthusiastic (173 reputation)SSC-Enthusiastic (173 reputation)SSC-Enthusiastic (173 reputation)SSC-Enthusiastic (173 reputation)SSC-Enthusiastic (173 reputation)SSC-Enthusiastic (173 reputation)

Group: General Forum Members
Points: 173 Visits: 654
Hi zeeaay,

I´m facing the same problem. I opened the advance editor of every step and refresh the metadata but in the Ole Db Destination the metadata is wrong. I'm also using CSV files as the source. It is just a warning and I know that it won't be any error, but a warning symbol in the DFT is not nice.

Any comment would be appreciated

Kind Regards

Paul Hernández
SZARS
SZARS
Forum Newbie
Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)

Group: General Forum Members
Points: 9 Visits: 76
So would some one a guru of SSIS will be able to rescue us out and the nation. Please do share your success experience and expertise achieved over the years.
sometimes minds just gets frozen and there is no bail out.
Paul Hernández
Paul Hernández
SSC-Enthusiastic
SSC-Enthusiastic (173 reputation)SSC-Enthusiastic (173 reputation)SSC-Enthusiastic (173 reputation)SSC-Enthusiastic (173 reputation)SSC-Enthusiastic (173 reputation)SSC-Enthusiastic (173 reputation)SSC-Enthusiastic (173 reputation)SSC-Enthusiastic (173 reputation)

Group: General Forum Members
Points: 173 Visits: 654
Hi all,

Finally, I just erased the Ole Db destination, added a new one and that's all, problem solved. It seems like a sincronization problem between the metadata and the UI. Please let me know if it works for you?

Kind Regards,

Paul Hernández
SZARS
SZARS
Forum Newbie
Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)

Group: General Forum Members
Points: 9 Visits: 76
Hey Paul,
thanks a bunch. I will try and let you know how it comes up.
Regards,
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search