hi, tx for the solution. I have each query inside a transaction and commit them after evry 10000 records are processed. So will a HWM of 15000 help to resolve table lock promotions and run processes concurrently?
Main Topics
Browse All TopicsHi,
cud someone let me know what the ideal lock promotion HWM threshold is in Sybase. Im looking at running a stored procedure concurrently with different input pararmeters and so DONT WANT one instance lock the tables. thot increasing the row lock promotion threshold would solve this problem but am not sure what is the ideal value for HWM. will there be any performance degradation in increasing this threshold?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: sysdbaPosted on 2009-10-14 at 04:42:26ID: 25569345
page lock promotion HWM (high-water mark), together with the page lock promotion LWM (low-water mark) and page lock promotion PCT (percentage), specifies the number of page locks permitted during a single scan session of a page-locked table or index before Adaptive Server attempts to escalate from page locks to a table lock.
page lock promotion HWM sets a maximum number of page locks allowed on a table before Adaptive Server attempts to escalate to a table lock. When the number of page locks acquired during a scan session exceeds page lock promotion HWM, Adaptive Server attempts to acquire a table lock. The page lock promotion HWM value cannot be higher than number of locks value.
The default value for page lock promotion HWM 200 is appropriate for most applications. You might want to raise the value to avoid table locking. For example, if you know that there are regular updates to 500 pages of an allpages-locked or datapages-locked table containing thousands of pages, you can increase concurrency for the tables by setting page lock promotion HWM to 500 so that lock promotion does not occur at the default setting of 200.
But effecting lock granularity will effect performance, not necessarily degrade it but will effect. when database engine esquires lock it is spending some resources the lower lock granularity is more locks it should esquire thus spend more resources. in your case instead of 1 table lock you will use 500 page locks. monitor CPU consumption it will need more CPU
Use sp_sysmon to see how changing page lock promotion HWM affects the number of lock promotions. sp_sysmon reports the ratio of exclusive page to exclusive table lock promotions and the ratio of shared page to shared table lock promotions.