I have read it, and I do not see a solution to my problem overthere. Why... With just a OLEDB Source and OLEDB Destination I am able to redirect only the truncation records as long as there are also conversion errors present. If there are only truncation errors I cannot get them redirected into the Error Output. So I agree because there is no truncation option to set on OLEDB Destination I am not able to find only the truncation errors (having no converion error present). Have you some other solution to this? Thanks.Krystof Malak

With just a OLEDB Source and OLEDB Destination I am able to redirect only the truncation records as long as there are also conversion errors present. There is no link whatsoever between conversion and truncation errors. You had NO errors redirected due to truncation. All your errors were conversion errors. You are complicating the problem by not being able to understand this difference. The above article provides a solution to your problem. Jeff Wharton MSysDev (C.Sturt), MDbDsgnMgt (C.Sturt), MCT, MCPD, MCITP, MCDBA Blog: Mr. Wharty's Ramblings MC ID: Microsoft Transcript Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker

I do not see tha solution. If there are only truncation errors then I CANNOT get them redirected to the OLEDB Destination error output table. If there are not only truncation errors, but also conversion errors then I CAN get them redirected to the OLEDB Destination error output table. In my case (with Maximum insert commit size = 2147483647) I CAN get only the conversion and truncation errors into the OLEDB Destination error output table, so only incorrect data (and not correct data also as the article suggests) My conclusion is that as long as I do not have at least one conversion error I will not get the truncation errors into the OLEDB Destination error output table. So the only link that I see betweeen the conversion and truncation errors is in the way that OLEDB Destination can handle those two types of errors, or truncation error is not an error according to the OLEDB Destionation? So, please, explain to me what I am missing here. Thanks Krystof Malak

If there are only truncation errors then I CANNOT get them redirected to the OLEDB Destination error output table. Not correct, the article explains how to do this If there are not only truncation errors, but also conversion errors then I CAN get them redirected to the OLEDB Destination error output table. Not correct. Truncation errors have nothing to do with conversions errors. In my case (with Maximum insert commit size = 2147483647) I CAN get only the conversion and truncation errors into the OLEDB Destination error output table, so only incorrect data (and not correct data also as the article suggests) Did you actually read this article properly? It clearly states that you need to add an additional OLE DB destination and set its Maximum insert commit size =1. Then you'll be able to trap truncation errors. My conclusion is that as long as I do not have at least one conversion error I will not get the truncation errors into the OLEDB Destination error output table. Not correct. There is no link whatsoever between conversion and truncation errors. So the only link that I see betweeen the conversion and truncation errors is in the way that OLEDB Destination can handle those two types of errors. Once again, there is NO link whatsoever between truncation and conversion errors. or truncation error is not an error according to the OLEDB Destionation? Not correct, the article explains how to trap these errors. So, please, explain to me what I am missing here. What you are missing is the fact that there is absolutely no link whatsoever between conversion and truncation errors. Unless you can understand this, you will never be able to implement a solution that catches truncation errors. I'm really sorry but I can't assist you any further as I seem to be telling you the same thing over and over again however you're not listening. You are fixated on linking conversion and truncation errors and you're not prepared to use anything other than 1 OLE DB Source and 1 OLE DB Destination. Based on this, there is no way that you'll be able to trap truncation errors unless you're prepared to understand the difference between truncation and conversion errors and understand that you can't just use 1 OLE DB Source and 1 OLE DB Destination. To assist you further, please have a look at these Google search results and read up on this issue http://www.google.com.au/search?source=ig&hl=en&rlz=&=&q=ole+db+destination+truncate+row+redirect&aq=f&aqi=&aql=&oq= Jeff Wharton MSysDev (C.Sturt), MDbDsgnMgt (C.Sturt), MCT, MCPD, MCITP, MCDBA Blog: Mr. Wharty's Ramblings MC ID: Microsoft Transcript Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker

Hi in your case if you trying to place the corrected to 123,55 value in to the numeric field of data base then {The symbol comma (,) is not allowed } is not allowed so this may be the error, Check it once.. by removing the commas.. let me know if I am wrong

Hi in your case if you trying to place the corrected to 123,55 value, the , is not allowed so this may be the error, Check it once.. If you read this thread correctly, you'll see that the OP has fixed that error and they are now trying to redirect truncation errors.Jeff Wharton MSysDev (C.Sturt), MDbDsgnMgt (C.Sturt), MCT, MCPD, MCITP, MCDBA Blog: Mr. Wharty's Ramblings MC ID: Microsoft Transcript Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker

Hi, I am loading data from the OLEDB source to the OLEDB destination with all errors sent to the other OLEDB destination via Error Output (Redirect Row). 1. First run. After the first run there are both conversion (alphanumeric value into numeric column) and truncation (101 characters long value into 100 characters long column) errors generated. 2. Second run. I remove manually the incorrect data that caused the conversion errors in the first run. After the second run I do not see the conversion errors any more (CORRECT) and I do not see the truncation errors any more (NOT CORRECT?!!!!!) I do not understand why I do not see the truncation errors any more. I do want to see them. Thanks.Krystof Malak

Maybe the records you modified were also the records causing the truncation errorsJeff Wharton MSysDev (C.Sturt), MDbDsgnMgt (C.Sturt), MCT, MCPD, MCITP, MCDBA Blog: Mr. Wharty's Ramblings MC ID: Microsoft Transcript Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker

I thought till now that using Error Ouptut (Redirect Row) I am able to put aside both conversion OR truncation errors. Are you saying that if the row does not contain a conversion error but only the truncation error then no row will be sent to the other OLEDB destination? What should I do to find all potential truncation errors in this secnario? ThanksKrystof Malak

I thought till now that using Error Ouptut (Redirect Row) I am able to put aside both conversion OR truncation errors. Are you saying that if the row does not contain a conversion error but only the truncation error then no row will be sent to the other OLEDB destination? What should I do to find all potential truncation errors in this secnario? Thanks Krystof Malak No I'm not saying that at all. What I am saying is that maybe the records that were causing the conversion errors were also causing the truncation errors and by deleting these records, no records contained data greater than 100 charactersJeff Wharton MSysDev (C.Sturt), MDbDsgnMgt (C.Sturt), MCT, MCPD, MCITP, MCDBA Blog: Mr. Wharty's Ramblings MC ID: Microsoft Transcript Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker

I DID NOT remove the records causing the conversion errors. I just corrected their values, for example (123,55) corrected to 123,55. In this case the conversion error row contains the truncation error aswell. Thanks.Krystof Malak

Can you verify that records containing 101 characters did not get redirected i.e. find a record that has 101 characters and see whether it was redicrected to the error outputJeff Wharton MSysDev (C.Sturt), MDbDsgnMgt (C.Sturt), MCT, MCPD, MCITP, MCDBA Blog: Mr. Wharty's Ramblings MC ID: Microsoft Transcript Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker

I confirm that : 1. having 10 records with both the conversion errors (10x in the column A) and the truncation error (1x in the column B) I see in the error output table 10 records, i.e. 9x saying '...conversion error...', and 1x saying '...truncation error...' (this record also has the conversion error) 2. after correcting the values causing the conversion errors (10x) I do not see any record in the error output table, i.e. no truncation error sent to the error output, but the value of the column B is truncated from 101 characters to 100 characters. ThanksKrystof Malak

To me it sounds like the only reason why the record with the 101 characters was sent to the error row was because of the conversion error, not the truncation error. Please double check that you haven't accidently set the On Truncation Error to a Ignore.Jeff Wharton MSysDev (C.Sturt), MDbDsgnMgt (C.Sturt), MCT, MCPD, MCITP, MCDBA Blog: Mr. Wharty's Ramblings MC ID: Microsoft Transcript Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker

Whare exactly to set this property? On what control? Thanks.Krystof Malak

In the exact same place that you set row redirection. http://msdn.microsoft.com/en-us/library/ms186998.aspxJeff Wharton MSysDev (C.Sturt), MDbDsgnMgt (C.Sturt), MCT, MCPD, MCITP, MCDBA Blog: Mr. Wharty's Ramblings MC ID: Microsoft Transcript Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker

Shortly I have the following: 1. OLEDB Source having all columns (Error, Truncation) set to Fail component in the Error Output 2. OLEDB Destination having just one row set to Redirect row in the Error Output, so this error output is the input for another OLEDB Destination I see in the msdn link that the error handling is done on the OLEDB Source level, and not on the OLEDB Destination level as in my case, where I do not see all the columns but just one row (Redirect row). Maybe I misunderstand the error handling. What I what to achieve is to save all conversion or truncation errors. I could send you some printscreens if you like. ThanksKrystof Malak

OLE DB Destination's do not have a setting to redirect on truncation. It just redirects on error. For this to work though, you need to set the appropriate values on the destination. Have a read of http://agilebi.com/jwelch/2008/09/05/error-redirection-with-the-ole-db-destination/ Jeff Wharton MSysDev (C.Sturt), MDbDsgnMgt (C.Sturt), MCT, MCPD, MCITP, MCDBA Blog: Mr. Wharty's Ramblings MC ID: Microsoft Transcript Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker