Hi,
I am using an OLEDB source to run a stored procedure, which returns records from a temp table. The destination table is exactly same as the temp table in the stored procedure. I've some collation settings on both the destination table and temp table, but both are exactly same.
I got Unicode to Non-unicode conversion error first. I dont know why it happened as there is no difference in source and destination table. I solved that issue using the data conversion component. Then I got the truncation error. I set the Ignore on Truncation on error output to get rid of that issue. Then the package executed without any problem. But all the nvarchar and varchar fields in the destination table got populated with only the first letter of data.
Any Idea?
hi
check the limits of the varchar values in the both tables and match them
|||Hi Ali Naqvi,
Thanks for your reply. Actually the problem was with a dummy SELECT statement that I put on top of the SP for getting the column metadata. Once I made the type casting to proper type and length inside the SELECT query, both unicode conversion error and truncation error are gone. Now the package is running fine without any error.
No comments:
Post a Comment