DSXchange

Proper key-based partitioning makes sure that, when a key value comes in from the left input, it can be sure that all occurrences of that key from the right input are on the same node as the value on the left input. There is no auto-match in mappings in the Join stage. It just appears that way. You ...

Why not just perform a Usage Analysis (in Manager) on the table that contains the changes? If you've been diligent with loading table definitions into jobs from the Repository, then Usage Analysis can give you a list of all the jobs that touch that table definition. Indeed, it even reports which col...

"Give me the solution"?!!!

Sir, that's what I do for a living. Only it's not "give" - it's "sell".

This site is totally supported by volunteers. You would do well to moderate your tone.

Ignoring node pools, every Lookup is performed on every node, because the Lookup stage executes in parallel. More nodes equals fewer rows per node to be processed and therefore linearly decreasing processing time (assuming even partitioning). On the other hand, the total amount of memory required fo...

Alternatively write your own.

Welcome aboard. You are going to need some kind of database stage to get the data out of the tables, so I am presuming you are using ODBC stage for this. If both tables are in the same database, best practice is to perform the join in SQL, particularly if it can be aided by indexes in the database. ...

They *should* be OK - after all, your profile in QualityStage Designer specifies where the master project directory for QS is on the server. A niggling thought that you may need to be careful with environment variables PATH and LD_LIBRARY_PATH - maybe set up different users for each with different ....

How about a competition for the most nested quoted answers in a single post? The "winner" gets their premium membership renewal fee multiplied by the number of nested quoted answers, on the basis that it wastes server space proportionately. For example, if they have quoted seven answers in one post,...

The error message is unrelated to your original request. The error message is a complaint about use of the Oracle-specific syntax for outer join - with an ANSI join you need to specify the join in the FROM clause, for example FROM DVE.a a LEFT OUTER JOIN DVE.b b ON b.USER_ID = a.EDSNET_ID The rest o...

It's not possible with DSJobReport. What you get is what you get. If you want something else, investigate ETLstats or search the forum for DIY techniques.

Fmt(expression, "20R9") will give you nine digits after the decimal place. You may wish to apply a TrimF() function to that result.

I would like to have $PROJDEF (and maybe $ENV and $UNSET as well) able to be used as default "values" for List type parameters. Currently this is not possible, because only values from the list may be selected as default.

Take the job parameter out of the job. That is, delete it from the Parameters grid.

Then use Add Environment Variable command button to add $APT_CONFIG_FILE. Set the default value of the newly-added job parameter to the special value $PROJDEF.

Because CHAR(12) requires twelve characters and APT_STRING_PADCHAR is set to \x00.