August 7, 2025 at 1:42 pm
hi , every time i go back to an ssis pkg that is under construction, at least one column in a tsv needs to be reset in the advanced properties of the oledb source from 50 bytes to 256. Even though last time i edited it, i saved the pkg.
why is that happening? Today , i went ahead and opened the derived column component and oledb destination following it to see if maybe that might alleviate the issue next time.
also, i'm noticing each time i open the df, even after a save and reset of that col's lengths, i see a yellow triangle on the flat file source warning in the intellisense that external columns are out of sync with the data source cols. And yet, that source to dest flow runs when i debug.
im also noticing that when prompted by ...is out of sync , do you want to... and i click yes, the wrong col length is put back in advanced i/o city col. so its actually better for the pkg's success to leave that warning as is.
August 8, 2025 at 2:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply