Archives of the TeradataForum

Message Posted: Thu, 19 Jun 2003 @ 14:26:55 GMT

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

Srini, you may already have considered this but aborting a long-running process can be catastrophic to your system if it causes a rollback. Aborting a select statement is fine but you had better hope the session to be aborted is not doing an insert into a populated table! If the "select" part of the insert/select is complex enough, it may consume enough CPU seconds to cross your threshold while processing.

A safe automated abort process calls the APIs to verify that the session's SQL is only selecting before it aborts. To avoid a rollback, it would not abort a session doing an insert, update or delete. Do everything within your power to avoid rollbacks, even if that includes allowing the occasional bad SQL to complete. Automating aborts seems dangerous - I'd rather personally evaluate what the session is doing before I issue an abort but that's just me.

Adam
Advanced Teradata Certified Professional

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