DSXchange

Inner join during extraction. Do it in the database, where it can be supported by indexes, rather than in DataStage, where it can't.

Otherwise use pretty much exactly what you've specified as output column derivation experssions in a Transformer stage.

Where do you imagine the third decimal place is going to be generated from? You've summed numbers with a scale of 2. There is no third decimal place.

I read the question differently. I understand that the question is whether it's possible to recover log events that have been cleared.

The answer to that question is NO.

Bad news 1: it's not available until version 8.0.
Bad news 2: the one in version 8.0 is not complete.

Hi, I also have same impression as the partioning does not depend upon the business logic. But it has a big impact on the column data on which u mentioned the partion key. Hope u got it.... Subrat U hasn't posted in a white. Why do you hope U got it? As far as I can tell U never mentioned anything ...

A Data Set is a parallel structure which stores data on all nodes on which processing is occurring. It preserves internal data types, partitioning and sorting. Indeed the operator used to move data between physical and virtual Data Sets is the copy operator. Sequential files exist in only one place,...

Verify that your project's indexing is intact.

Yes, please do. Your job design without them is gobbledegook, as you can see.

You've got IP_ID_REL and IP_ID in different order in the Columns grid and in the SQL, so that the parameter markers are not lining up correctly.

You identify the key column(s). The characters from those columns are used as input to a hashing function, which always returns the same uint32 value (the "hashvalue") for any given set of characters. This "hashvalue" is divided by the number of partitions and the remainder is the partition number t...

The data type between the ":" and the "=" in a Specification is that of the output field, not that of the input field. Therefore, if the output field needs to be integer, then int32 (etc.) must be the data type. There is no implicit convertion from string to integer, so you must provide a function s...

You can say that. But it would be better to exclude Build stages as well, for these also contain C++ code and therefore require the compiler.

I just provided a briefing on the differences (in Bangalore) which took half a day. There is no way I am going to attempt the same through DSXchange! My fingers would wear out. Why is it so urgent? Err on the side of caution - don't upgrade till you think you know enough about the new version.

Select the table definition in which the field occurs and perform a usage analysis on it. When a usage analysis is performed on a table definition it reports the columns from that table definition that are actually used in the job. Having performed the usage analysis, go to its File menu and choose ...

A more detailed specification for a start.

Does "format matching" simply refer to the fields in the file (the right number of fields, the correct width for fixed-width, etc.) or does it refer to something more specific on a per-field basis?