|
Archives of the TeradataForumMessage Posted: Mon, 25 Feb 2008 @ 13:11:27 GMT
Hi guys, Just starting with using TPump, so I'm a little unsure on a few things. Firstly, can anyone tell me what these do :- IGNORE DUPLICATE ROWS IGNORE MISSING ROWS IGNORE EXTRA ROWS We're using an Upsert an I'm not sure what these options can do for me. Also, if we've got a Multiset Table with only a NUPI on the table, so whilst the Upsert will mention the full logical primary key, does the table actually have to have a unique constraint added to the table ? Lastly, I've noticed that a Macro is created by the utility, which covers the Update and Insert statement, having an Input parameter for each column being Updated or Inserted What parts of the Tpump script can I then change ? For example, do I just replace the Insert and Update statement with EXEC GeneratedMacro(field1, field2,etc); ? Can I then do away with the .LAYOUT definition or is that still necessary for invoking the Macro, detailing what the input is ? I've currently got this in the script : DO INSERT FOR MISSING UPDATE ROWS SERIALIZEON (JNY_OBJ_ID) Does this need to be moved or changed when invoking the Macro ? Were currently using a batch file to 'feed' the Tpump job. I assume that once the file and been read and processed by the TPump job, the TPump job itself will stop and have to be re-started in order to read a new populated file ? Correct ? Any examples of showing the change from moving from the basic TPump script to invoking the generated Macro would be much appreciated. Regards, Dave Clough
| ||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | ||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | ||||||||||||||||||||||||||||||||||||||||||||||||