Archives of the TeradataForum

Message Posted: Mon, 28 Oct 2003 @ 02:15:21 GMT

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

I find Locking Logger to be a really valuable tool to identify possible locking contention issues. I believe it is in the only tool available in Teradata that provides you with a history of lock contention (albeit a brief history).

Locking contention typically should be kept to a minimum for optimal throughput. Almost all locking contention issues can be avoided through job scheduling. The remaining lock contention issues I see are against DBC tables such as AccessRights, by and large, these tend to be fleeting and are typically not typically a concern unless they are occurring often. This might be an indication that the AccessRights table might not be as concise as it could be or the current strategy for assigning AccessRights might not be optimally effective.

I always look at the DELAY column as a first step in analyzing the impact of lock contention. Obviously, the longer the DELAY, the more cause for concern there is.

I'm not sure if I exactly answered your question. But I think that there is no firm rule of thumb for "an acceptable amount of blocking/locking". My goal is always to minimize it/eliminate it to the greatest extent possible.

Regards,

Thomas F. Stanek
TFS Consulting, Inc.

www.tfsconsulting.com

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