data type gets lost in data flow
-
Hi, in a simple oledb source->derived column->oledb destination data flow, 2 of my date columns that are converted to varchar, format 101, in the source view, ultimately seem to end up as unicode in the oledb destination. And that seems to bring down the pkg. everywhere else they are dt_str length of 30 .
I had to rewrite the pkg from scratch to get it to run. You can see the underlying destination's xml code below.
The only weird thing here is that i chose to convert in vs's project properties from 2022 to 2019 because i opened this solution in vs 2022 but planned to deploy to a 2019 server. there were a number of pkgs in the solution and if you want to call this "file corruption", it only occurred on the 1st pkg.
to make sure i wasnt dreaming, in advanced editor for the destination component, in the external columns folder, i saw Unicode string [DT_WSTR] for a length of 10 on both columns. i tried changing the data types there to dt_str length of 30, and saving but ssis reverted to unicode, basically ignoring the change.
Once isnt so bad, but it would be nice to know how to avoid or repair this in the future. Any thoughts?
Viewing post 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply