DSXchange

FYI - 0x20 is a space.

Split from this 7 year old semi-related post. Please just start your own topic next time for things like this.

I would suggest that, if at all possible, you let the stage generate the SQL whenever possible. Only supply "user defined" SQL for those situations when you have no other choice, for something that is not... generatable.

Can you clarify what exactly it is you mean when you say "remote deployment"?

Still gonna get the same answers that you got over on ITToolbox.

Today I create a job that uses the merge stage to join 3 different sources of data (datasets) and then loads into a target table. Because of the requirements of the merge stage I explicitly hash partition my source data, pre-sort, and remove dups. I run this using a single-node config file and proc...

Ray has already listed what you couldn't compile without a C++ compiler also installed.

These must be source SQLs, as in ones that provide data to the job so I'm assuming they are not appropriate for using before/after. If you don't want to go the 'union' route then perhaps the job can be 'looped' via a Sequence job that replaces the sql file each iteration.

Note quite sure how you got that from a reading of their post, Ray, they mention nothing about still planning on invoking the CoSort scripts. They are looking for advice on exactly what you mentioned - converting the work that CoSort does into DataStage. Off the top of my head, however, I have no id...

Then it's not supported it would seem. Why not just add a UNION ALL between them so they become a single Sql statement?

You'll find that basically every DS API function has an equivalent from the command line via dsjob.

I don't recall if that is an option when using a SQL file (always used it for a single statement) and I don't have any way to check right now. Only thing I can think of right now is to try two semi-colons as a separator: ";;".

I would say there is always a possibility. That possibility goes up with any tool if you are new to it and there's no-one onsite to mentor you. However, I wouldn't let that stop you... why solve only half the problem?

I guess they are wasting their time if in fact they are on the releases you mention. So... Prem?

Be aware that coding it with DSJ.ME as the job handle means it can only check the links in the job that called it. And that means you'd need to call this routine 'after job' in every job that you wanted to monitor. I prefer a 'post' process, something that you can run after your loads are complete t...