IBM Db2 - The Ultimate Database for Cloud, Analytics & Mobile
This is the last article in the series by Gareth Copplestone-Jones on locking for developers, and is a wrap up of miscellaneous points arising from previous articles.
The first item under discussion is row-level locking. I mentioned previously that the design default lock size should be page-level, with row-level locking only being used where justified. This is to reduce the CPU and elapsed time overhead typically incurred by row-level locking, and especially to avoid the data sharing overhead involved. The DB2 for z/OS documentation has further information about locking in a data sharing environment, but for the purposes of this article it’s important to stress that row level locking in a data sharing environment can and typically does introduce significant overheads.
Continue reading the final instalment in Gareth Copplestone-Jones series of blogs on DB2 for z/OS Locking for Application Developers.
Add a Comment