Question on Partitioning:: Full table lock or only Partition Lock?

General
Enthusiast

Question on Partitioning:: Full table lock or only Partition Lock?

I have been looking for answers to a basic question on table partitioning in Teradata. Can someone please shed more light. Here it is -

If we do Range Partitioning on a table based on Numeric values and then different jobs load data corresponding to different partition ranges in parallel - then do we get into a resource contention scenario OR do all parallel running jobs hit specific partition and only acquire lock on a particular partition. In short - the question is - while loading data into a partitioned table [in this case Range Partition], do we acquire a lock at the partition level and multiple programs can run in parallel acquiring lock at individual partitions OR the lock is acquired at whole table level and the parallel jobs get into a contention mode.

Ex: An error table where each program loads specific error information that is encountered based on error code. If the table is range partitioned on error codes of range of 1000s, will individual programs when run in parallel hit their specific partition acquiring only lock to it or they will acquire complete table lock and release them for subsequent jobs when error load is done.

Please advice.
2 REPLIES
Enthusiast

Re: Question on Partitioning:: Full table lock or only Partition Lock?

There is no partition level locking in Teradata - yet.
Enthusiast

Re: Question on Partitioning:: Full table lock or only Partition Lock?

All,
Have got a reply in an anlternative forum post by Carrie. If you wish to know the answer, please read on -

http://developer.teradata.com/blog/carrie/2009/11/collecting-stats-on-partition-for-non-partitioned-tables#comment-11858

@ Jim Chapman - Thanks for your reply!