DSXchange

it should generate the drop statement itself for all the tables your specifying for Mload........ for the before command we usually check the two options specified in datastage in the before tab.

which tables are being used in the Mload ? you have not mentioned the DUP tables etc. Try the Command RELEASE MLOAD TABLE IN APPLY.

How are you checking the data in TD ? if your using the SQL assistant you can set the options in the SQL assistant on how to display NULL's. i think yours might be set to empty string maybe? Is the data coming through ok as this does not seem to be a problem with the job itself and TD.

search for horizontal pivoting.............

Connector stage is actually the Teradata TPT API, which means although the protocols being used behind are fast export and fastload but it will be much faster than Multiload and Fast export itself as it creates multiple instances and then process the data (not to be confused with sessions). If the j...

there is no relationship. i think they are on a break

there is no log file created with the TPT stage. Although the detailed information can be seen in the director log of the job. what is the number of maximum sessions and sleep defined in the stage?

The usage of UPI or USI depends on what you really require and what the needs are in terms of performance. Performance is really an issue when we need to pull data out of a table join it to some other table etc. Primary key is just a concept to enforce uniqueness to a record and in TD we apply this ...

Just a bit of a shocker

by searching the forum :D

hash partitioning and sort ascending on all key columns with the sort stage for links going into the join stage would be a good idea

more flexible and less bugs as compared to the enterprise stage.

its a problem with your source data and not with the delimitation. Correct bad data and/or update processes.

they are two different products with two different architectures.