data type gets lost in data flow

Question

Post reply

data type gets lost in data flow

stan

Ten Centuries

Points: 1312
More actions
December 12, 2025 at 6:32 pm

#4699467

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 12 posts - 1 through 12 (of 12 total)

You must be logged in to reply to this topic. Login to reply

Site Owners SSC Guru Points: 80411 More actions · Answer 1

Thanks for posting your issue and hopefully someone will answer soon.

This is an automated bump to increase visibility of your question.

Steve Jones - SSC Editor SSC Guru Points: 740332 More actions · Answer 2

I had someone say to check the advanced tab in SSIS

https://x.com/fv439/status/2001016477722562647?s=20

stan Ten Centuries Points: 1312 More actions · Answer 3

thx steve, that link is taking me to adult content. i got out as fast as i could.

i always use the advanced tab for these kinds of things. So i dont think that is the path i'd want to follow, but who knows if the link you wanted me to follow had something eye opening to consider.

Steve Jones - SSC Editor SSC Guru Points: 740332 More actions · Answer 4

It's not adult content. X.com is formerly twitter.

It's this page

2025-12_0305

stan Ten Centuries Points: 1312 More actions · Answer 5

thx steve, yes i always go to advanced with things like this. in this case, in the final oledb destination, i change the data type in advanced and ssis ignores the change. in the next 6 posts , i show proof at least of what im seeing...