Archives of the TeradataForum

Message Posted: Fri, 21 Dec 2002 @ 02:28:09 GMT

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

Access Log is syncronous with the request, in fact the request is not allowed to succeed until the access log entry (if any) is sucessfully completed. Otherwise, creative people could start a query, get part of the answer and then abort it aborting the access log write as well. Not allowable.

Query Log is much more relaxed. It is buffered and written independently of the request because it's requirements are not as stringent. This also allows some buffered writes which improves the overall cost of the facility.

The priority of the logging cannot be controlled. It is an internal function. Even if the priority could be controlled, it would not change the *cost* of the logging. It might change the impact to other work but that is not likely as long as logging is not turned on for the very short requests (single row selects, Tpump,...).

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