Archives of the TeradataForum

Message Posted: Fri, 08 May 2009 @ 10:01:05 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

If you have a process is place then use a history table and move the old record to it before you store the new record. This is easy to do with Bteq or whatever the interface you build. If you have bunch of user that is doing it, create macro and give update /insert ability. Let the macro have the embedded logic and keep building your audit records. The other option is to enable Access Logging but remember if you are doing this for too many objects then it is going to be resource extensive task. Teradata no longer recommend this. If you don't have control over your user and the interface then yes trigger would be a solution too. You can do before Update/Delete and capture the records to log audit. If the volume of data is not much then keeping on the same table and inserting new records by expiring old will work as well. In this case you will need to have some kind of stored on table date. Hope this helps.

	<Prev	Next>		<<First	<Prev	Next>	Last>>