DSXchange

That is my understanding as well.

In other words, compressed using "the UNIX compress or GZIP utility" according to the manual. Meaning you would need to uncompress it first - to standard out and pipe it to orchadmin command. I assume.

Involve support. Google for "java.net.SocketException: Connection reset". See answer to your other file connector issue.

Perhaps you should show us the records at / around that count. Not much anyone can do except guess without any details other than an error message.

Same answer.

Not really seeing a question... but it sounds like you just need to use a sparse lookup.

I've never been a fan of those "dual action" methods, much preferring to do the determination myself of what was needed and then crafting the appropriate DML for each situation. And just to be anal, all a "key" field means is it can be used in a where to identify records to updat...

I have to ask... why not simply leave the Generate SQL option as "Yes"? :? Other than that, on your additional information points: 1. Okay 2. No clue what that means. Not available in table? 3. That's how an update works, the key fields are bound into the where clause 4. Again, that's how ...

Well... what "marketing cloud" exactly? What database sits in it? What sort of interface protocols do they support? ODBC, JDBC, something proprietary? You'll need to do some research.

Not that this answers your question but... your text files could certainly be made to reside in a database if that would help. :wink: And just to clarify, you're not looking for a token match (whole words) but rather a substring match? Asking because you have "Russian" as master data match...

PM sent.

We does! The DoD, to be specific. :wink: Heck, we weren't even allowed to write the damn thing, that had to come from our DBA team who then granted execute to our functional user. Surely they can do the same for you. Not sure what kind of issues cause your failures but they should be easy for the PL...

And yet you could easily raise the sizes in the source metadata then ensure all meet the target limits in the job before sending it on. This is a pretty standard method to do exactly what you need to do when dealing with flat files.

We went the stored procedure route as there was no way to win the grants battle needed to allow our single connection account the ability to truncate the tables it needed to. However, our works just fine - as in all the time and happily reports any problems up the food chain. Sounds like you just ne...