May 14, 2014 at 5:44 am
Hi,
I got below error when I upgrade SSIS Package from 2005 to 2008r2.
Truncation may occur due to inserting data from data flow column "ColXXX" with a length of 255 to database column "ColXYZ" with a length of 1.
In dataflow source is flat file and destination is OLEDB.
Please don't tell me to change in show advance editor --> Input output properties --> source output--> output columns
Because I have 705 warnings like this.
Thanks in Advance.
Venkat
May 14, 2014 at 6:07 am
There are blank values or spaces in the columns in your source file.Better to TRIM or limit the length to certain number as per your requirement using SUBSTRING.
--rhythmk
------------------------------------------------------------------
To post your question use below link
https://www.sqlservercentral.com/articles/forum-etiquette-how-to-post-datacode-on-a-forum-to-get-the-best-help
🙂
May 14, 2014 at 6:37 am
rhythmk (5/14/2014)
There are blank values or spaces in the columns in your source file.Better to TRIM or limit the length to certain number as per your requirement using SUBSTRING.
But this would not stop the warnings appearing.
If you are mapping from a source column of width x to a target with width y, where x > y, you will always get this warning AFAIK. To stop the warnings, you need to make x <= y ... somehow 😉
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
May 14, 2014 at 6:51 am
venkat5677 (5/14/2014)
Hi,I got below error when I upgrade SSIS Package from 2005 to 2008r2.
Truncation may occur due to inserting data from data flow column "ColXXX" with a length of 255 to database column "ColXYZ" with a length of 1.
In dataflow source is flat file and destination is OLEDB.
Please don't tell me to change in show advance editor --> Input output properties --> source output--> output columns
Because I have 705 warnings like this.
Thanks in Advance.
Venkat
You can also just make the destination columns 255 characters wide. Instead of 1, which seems a bit small.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
May 14, 2014 at 2:27 pm
I changed destination table column length to 255 but no luck
May 14, 2014 at 11:22 pm
Phil Parkin (5/14/2014)
rhythmk (5/14/2014)
There are blank values or spaces in the columns in your source file.Better to TRIM or limit the length to certain number as per your requirement using SUBSTRING.But this would not stop the warnings appearing.
If you are mapping from a source column of width x to a target with width y, where x > y, you will always get this warning AFAIK. To stop the warnings, you need to make x <= y ... somehow 😉
Sorry, I forgot to mention to limit the length equal to the target column length 🙁
--rhythmk
------------------------------------------------------------------
To post your question use below link
https://www.sqlservercentral.com/articles/forum-etiquette-how-to-post-datacode-on-a-forum-to-get-the-best-help
🙂
May 14, 2014 at 11:27 pm
venkat5677 (5/14/2014)
I changed destination table column length to 255 but no luck
Not sure.If you really have a luxury to change the length of destination table column.
However can you please provide more input like for a perticular column what is the datatype and length at source and also provide the same for respective mapping column at destination with the error / warning you are getting for that column.
--rhythmk
------------------------------------------------------------------
To post your question use below link
https://www.sqlservercentral.com/articles/forum-etiquette-how-to-post-datacode-on-a-forum-to-get-the-best-help
🙂
May 14, 2014 at 11:43 pm
venkat5677 (5/14/2014)
I changed destination table column length to 255 but no luck
What error you get this time? it should not be the same as the earlier one. but if it is then you mapping was not being updated on the destination. try to refresh the destination and execute the package.
May 14, 2014 at 11:55 pm
venkat5677 (5/14/2014)
I changed destination table column length to 255 but no luck
What do you mean? Was the warning message still this?
Truncation may occur due to inserting data from data flow column "ColXXX" with a length of 255 to database column "ColXYZ" with a length of 1.
If so, something is clearly amiss.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
May 14, 2014 at 11:56 pm
twin.devil (5/14/2014)
venkat5677 (5/14/2014)
I changed destination table column length to 255 but no luckWhat error you get this time? it should not be the same as the earlier one. but if it is then you mapping was not being updated on the destination. try to refresh the destination and execute the package.
Oops, sorry - I missed this. You make the same point as I have just made.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
May 15, 2014 at 12:01 am
venkat5677 (5/14/2014)
I changed destination table column length to 255 but no luck
Did you refresh the metadata of the data flow?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
May 15, 2014 at 12:11 am
Phil Parkin (5/14/2014)
twin.devil (5/14/2014)
venkat5677 (5/14/2014)
I changed destination table column length to 255 but no luckWhat error you get this time? it should not be the same as the earlier one. but if it is then you mapping was not being updated on the destination. try to refresh the destination and execute the package.
Oops, sorry - I missed this. You make the same point as I have just made.
no need to sorry, Thats mean we are thinking in the same direction :hehe:
😉
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply