DSXchange

I am curious why you are getting different counts update then insert mode and Insert then update mode. Both cases the count should be the same Not true. The outcome of each is entirely dependant on the unique constraint that you may (or may not) on the record. Understand that the first action must ...

Why not just if-then-else around the index function?

This is why surrogate keys were invented.

Is this field the last one in your record? I'm not sure what "ignored" might mean, it really should be there as data but your tool of choice may not be showing it. Try this in a transformer after the read and see if the entire value appears: Convert(CHAR(13):CHAR(10),"",YourField)

The Join stage requires sorted data, so you can either let the job do the sorting for you or you can ensure the data arrives sorted. Since you don't seem to have the space to do the former, let the original database sources do the sorting by ordering the output properly. Then you can put a Sort stag...

You asked for the general rule, which I gave you - they should match, and yes that includes order.

General rule? Match certain they match.

Ideally, yes, in a perfect world.

Start by posting your question in the Information Analyzer forum.

Try sliding the Columns tab over to the right to expose the "Contains Terminators" property. Enable it for that field.

Of course, you could always increase scratch space - more is better. And clearing it can be simple if it is dedicated scratch space. Does DataStage share that space with other applications? If not, if all that plays there are DataStage jobs, whenever there is a quiet moment when nothing is running y...

ray.wurlod wrote:You have another thread active on the quotes issue.

Actually, someone else is having a quotes issue and Pandeesh chimed in there... and now has his own version of the issue as well.

Eventually.

Three all day meetings suck.

... and off we go to the IA forum.

Seems appropriate - done.