Archives of the TeradataForum

Message Posted: Tue, 21 Aug 2007 @ 13:23:00 GMT

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

The DBQL tables do not appear to capture the rows affected by DELETE statements from what I can tell on my system (V2R6.1).

If your delete statement(s) in production are running as part of a batch in a BTEQ or stored procedure you can use the ACTIVITYCOUNT (ACTIVITY_COUNT in SPL) variable to capture the rows affected and log this into a log table for later analysis. Other options include issuing a SELECT COUNT(*) against the table(s) affected before and after the DELETE statement is issued and capturing it in a log table.

Hope this helps.

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