DSXchange

Show us precisely how you specified the range lookup in the Lookup stage.

Welcome aboard.

My guess would be that the difference represents the overhead of compressing the data.

ODBC specifies an upper limit on the size of buffers that can be transmitted. From memory it is something like 8KB per row.

These defaults can be overridden in the uvodbc.config file. From memory the descriptor names have the form MAX...BUFF (you can Search DSXchange for the actual names).

Just as a matter of interest, how much available memory does the client machine have?

What's different between the two environments? Hint: "nothing" is not the correct answer.

That's basically it, although your constant will be 0.000001. Make sure that your stage variables, if used, are big enough (for example Decimal(26,6) data type). Make sure, too, that your format strings include specification of the fractional seconds. As a single expression: DecimalToTimestamp(Times...

Gold coloured, perhaps.

You should be able to use any legal SQL statement if you are using user-defined SQL. The columns in your metadata must match the columns returned by the SQL statement.

It would certainly explain the difference if the CRC32 function operates on bytes rather than on characters. The non-NLS and NLS byte streams are very likely to be different even for "extended ASCII".

Have you filled in the state file (or sequence) information on the Surrogate Key tab?

I've always found that IN doesn't really seem to be supported because the commas interfere with the data type check. You can, however, encapsulate the entire WHERE condition in a job parameter, or even the entire SQL statement.

Not legally, except for Sequential File stage (set current as default). You have to train your developers better. A baseball bat may help.

You can't Trim a Decimal.

The leading zeroes are displayed by DataStage to verify that precision and scale are being handled properly.

You can only remove the zeroes if the data type is string (or, I believe, integer) of some sort.

Use the shell variable $? to report whether orchadmin dump was successful.

Not really, although to use them you need plenty of memory - enough for the 4GB on top of whatever else is happening.