DSXchange

well if its just a simple update select the method" update" from the drop down list and it should work ok.

Paste the entire code generated by the stage. What areyou trying to achieve here as you are deleting, updating and inserting at the same time ?

you can write your own ultility which can do this for you. thats what has been done in the project i am working on right now. :D

specify the command in the job properties tab (either in the before or after job ) Select Execsh in the drop down list and infront of it specify the command you want to execute

by setting up failure property in lookup stage to true ?

There is a problem in the query you have submitted. It is not being able to prepare the work table accordingly and thats why it is giving and error.

Which teradata stage are you using ? This is a common error if your using the MLoad stage. The reason is associated with huge volumes of data. Try unchecking the "Use Named Pipe" option and run the job again. Should be ok.!

Which teradata stage are you using ? This is a common error if your using the MLoad stage. The reason is associated with huge volumes of data. Try unchecking the "Use Named Pipe" option and run the job again. Should be ok.!

Doesn't the number of sessions we specify in mload script represent parallelism???. Nope.The number of sessions define connections to TD, not how parallelism or degree of parallelism is controled and achieved. IF "sessions" were controlling parallelism one could use Mload stage in server ...

Well it will only create it once you specify it just like you do while writing a multiload script. This is useful in scenarios where one would be interested to make these tables in specified databases and name then according to a particular naming convention for the project. Teradata Certified Master

I know there are alot of post here pertaining to project corruption but most of them just point to another post and when you go on there, there is no solid solution to the problem. So would someone or all of us be kind enough to constibute to this one and post thier experiences on this so the inform...

Yes you do need to put a non processing state( passive stage) between two processing stages( active stage). in the server job you could avoid this by allowing inter process communication but for parallel jobs i dont think we can do that hence we need to explicity insert a passive stage to avoid erro...

it would depend on several factors such as how good your hardware is ? network ? how well your jobs are designed / tuned ? . i don't think there is a general answer to this.

it would depend on several factors such as how good your hardware is, how well your jobs are designed / tuned . i dont think there is a general answer to this.