DSXchange

Chetan.C tells us that the table design has yet to be defined. I think that doing that is the absolutely vital first step - what information about data errors does Chetan.C need to capture? This is not something we can do (in spite of having some experience in these areas). Chetan.C must come up wit...

Who else's manager might be sending them to the conference?

Probably, because you are parsing in parallel mode. But, as Craig notes, you won't notice much of a difference with small data volumes.

Welcome aboard.

There are over 250,000 answers to be found on DSXchange, including the answer to your question. In the menu at the top of the page is a link to the Search facility. (Tip: prefer Exact Search whenever possible.)

Read Chapter 2 of Parallel Job Developer's Guide to learn how Decimal (and other) data types are stored. This should answer your question.

On the Stage Properties tab you will find the ability to perform Mapping.

I suspect your assertion that the servers are the same in all respects will turn out to be incorrect. First off, how are you measuring "performance"? What actual measures are you using to assert "10 times worse"? What IS different? For example do both servers have the same NICs, ...

Short answer, posted many times on DSXchange, is that computers necessarily can not store floating point numbers perfectly accurately. They are limited by the sizes of the binary mantissa and exponent.

Try re-compiling the job. Fault type 11 is an access violation (SIGSEGV = 11) so there may also be a memory issue that you will need to resolve - perhaps an attempt to put too large a data item into a target or a null into a non-nullable field.

Quite simply a Parameter Set is not a job, and there is no option in dsexport for exporting a Parameter Set.

ISA Lite does very many things, as you'll see when you run it and look at its menu. As for your specific requirements, I don't know off the top of my head, but those things are readily determined by inspection. Actual values in use (in shared memory) from uvconfig can be determined using the analyze...

Usually the results directory is determined by %TEMP%.

This will become clearer once you've run ISALite - it is quite comprehensive in its reporting. You can in most cases readily infer the source.

I agree with your summation.