DSXchange

What is the actual data type in SQL Server?

You could always try that. If you do, make sure you remove all traces of the old client before you reinstall - and that means using regedit and also deleting leftover directories / files as well.

If it's just a problem for your installation, I'd suggest trying a reinstallation of the client right over the top old the old one.

The Field() delimiter must be a single character. So either convert all of the occurances of "%%%" down to a single "%" or offset the "field" that you ask for:
In other words, 1 gets field 1, 2 gets field 4, 3 gets field 7, etc.

Then please mark this as Resolved using the button at the top of the screen.

Right... wasn't sure if that meant the metadata was wrong in the job and they fixed it or if indeed some other job created one with the same name and the wrong metadata. If the latter, then you would need to find the culprit to resolve it, that or rename the hashed file in these jobs to be unique.

True, we can just suggest general solutions since we don't know the specifics of the 'load' being done here. And the 'skip' solution requires a static source to ensure one run's 38th record is the same as every other run's 38th record.

So, is this resolved? I can't... quite... tell. If so, please mark it as Resolved using the button at the top of the screen. If not, let us know.

Delete the 37 then rerun. Add a 'number of records to skip' job parameter and use that in a constraint.

Also - double-check you don't have another job building a hashed file with the same name but with different metadata. It happens!

And please DON'T SHOUT.

FYI - a "trick" I use - you need to start a 'reply with quote' session to take a proper look at the example. Without code tags, all extra spaces are always removed by the forum software. Then you'll see it's not about trailing spaces but rather internal spaces. cold ice land cold ice land ...

Didn't ask about a constraint, but rather the metadata. And again - what is your proof that it 'picks column next to it'?

Depends on what you mean by 'merge' so best to define that. Perhaps use one in a Lookup stage and join to the other in your input stream?

And still, as noted... wrong forum.