Archives of the TeradataForum
Message Posted: Wed, 30 Jul 2003 @ 18:52:06 GMT
Our ETL process is typical batch-processing after hours. We've got file feeds from disparate sources arriving at all times of the night. AutoSys handles this nicely, except for the times an operator sends yesteday's file and then, oops, sends the correct file.
My question to the group is: what processes, safeguards do you have to prevent this from happenning? Obviously, the remedy is to restore the corrupted Teradata tables and re-run the ETL jobs w/correct files.
How rigorous are your checks and balances for ETL? What's in place to catch 'anomolies' like this?
any insight would be appreciated.
James Kim Poley
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|