 |
 |
Archives of the TeradataForum
Message Posted: Thu, 26 Aug 2004 @ 13:54:27 GMT
Subj: | | Data Integrity Handling |
|
From: | | Tony Howe |
I have a question for other Teradata warehouse customers when having to do updates to your warehouse outside the normal process in order to
correct a data integrity problem, how do you handle logging these type for future reference, etc. We were looking at using Triggers and logging
to a "shadow" table that looks like the real table, but other are afraid triggers may perform badly.
Thanks in advance,
Anthony S. Howe
Teradata Certified Master
Teradata Database Administrator
Highmark, Inc.
| |