Archives of the TeradataForum

Message Posted: Fri, 08 May 2009 @ 10:02:15 GMT

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

Are you looking for an audit trail of the SQL or capturing the data as it was before the change?

DBQL or Access logging would capture the SQL that was submitted. DBQL would provide you with more detailed information about the client submitting the SQL.

There is a wealth of information available online and in books regarding how to handle slowing changing dimensions or changes to your fact tables in your data model.

As for direct updates to tables from users via ad hoc SQL a trigger would probably be preferred. You can't rely on a human with direct access to your tables to have the due diligence to write to a separate audit table or properly handle expiring the previous record via an UPDATE and a separate INSERT of the new record.

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