DSXchange

... or just search here for something like "supported compiler".

The best answer is "it depends". If the database server has spare capacity and/or if the join columns are indexed then chances are that the join will be resolved faster in the database. But the job will have to wait until the first row is delivered from the database.

How many client users are you licensed for? This sets an upper limit on the number of machines that may simultaneously be connected.

Have you accessed the manuals or on-line help, or taken any of the available training classes?

Please be more exact in your choice of post subject. It will assist future searchers.

Determine the job number from the DS_JOBS table then look in subdirectory RT_SCnnn (where nnn is the job number) in your project directory on the server.

Have you accessed the manuals, the on-line help or taken any classes?

Please do not confuse processing nodes with partitioning. There are several different ways data may be partitioned over the available number of nodes. The number of nodes is specified (via the number of node names) in the configuration file currently being used. Partitioning is the process of spread...

Set your VMware image memory sizes as follows.
Minimum 2GB for client (3GB recommended)
Minimum 3GB for server (8GB recommended)

Your expectations are correct. Is this version 8.0 or 8.1? There were some SCD problems in 8.0 - check with your support provider.

Well, it can count missing values and count non-missing values in Calculation aggregation. If you have no missing values then the count of non-missing values will be what you want. If you do, you could add both counts in a downstream Transformer stage.

You can't directly.

You could take an export of the project and search the export file for the data set name, then figure out in which job's scope it occurs.

And remember that there's usually more than one job.

No, you simply have to Sum a column whose value is always 1. This is the same result as Count. You can create such a column in an upstream Column Generator stage.

Use your Import menu to import an Orchestrate table definition and point the dialog to the ".ds" file that describes the Data Set. If this has already been done, then use a Where Used analysis to determine which jobs use the Data Set. It's usual that at least two jobs touch a Data Set - on...

I don't have the chance to try this, but you might try No promises.