Question
3
Replies
193
Views
Posted: September 25, 2019
Last activity: September 30, 2019
Closed
Blocking on pr_sys_locks and pr_sys_locks_sla tables
I'm DBA managing PEGA databases, recently we've noticed increased blocking on our SQL server database on these two pr_sys_locks and pr_sys_locks_sla tables. The below delete command is running but not doing anything for long time blocking other transactions.
(@P0 varchar(8000))delete from dbo.pr_sys_queue_sla where pzInsKey = @P0
Any idea why it's holding locks for so long? shouldn't it delete the row immediately?
Moderation Team has archived post,
Close popover
This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Posted: 1 year ago
Hi,
You can refer below Article. It may be useful
https://community.pega.com/support/support-articles/delete-prsyslocks-causing-db-blockage
Posted: 1 year ago
Can you please check if you are getting any exceptions from DB side? That may give us some idea on this.
what is your Pega version? Here is another related post: https://community1.pega.com/community/pega-support/question/heavy-sql-db-resources-consumption-delete-dboprsyslocks