 |
 |
Archives of the TeradataForum
Message Posted: Wed, 24 Jun 2009 @ 14:03:49 GMT
| Subj: | | Re: ET in Teradata DELETE MLOAD |
| |
| From: | | Dieter Noeth |
Victor Sokovin wrote:
| | Good question. I don't think I ever had to inspect the ET table after the MLOAD DELETE so don't have ready-to-use examples but I can
imagine it may possibly be populated by rows which were not deleted due to, say, potential violation of hard-coded referential integrity with
other tables. Not that I had to use the latter in Teradata either so my suggestion is purely hypothetical and requires validation by
experiments. | |
Hi Victor/Anomy,
i wondered about that ET table for years and still don't have any satisfying answer :-)
One of the proposed answer was: A programmer just forgot to remove it when changing source code from IMPORT to DELETE MLOAD...
At least it can't be Foreign Keys/Triggers, because both are not supported by MLoad, so it's one of those "features".
Dieter
| |
