Question4Replies157Views PradeepPydi Member since 2017 204 posts Anthem Posted: 1 year agoLast activity: 1 year 2 months ago Closed Heavy SQL DB resources consumption @ delete from dbo.pr_sys_locks .Hi Team,Heavy SQL DB resources consumption (along with deadlocks) has been observed during the below mentioned query execution (Nothing reported by AES though)delete from dbo.pr_sys_locks where pzInsKey = @P0 and pxOwnerId = @P1 Please suggest the scenarios during which this issue might happen and remediation recommendations ?(PRPC731,MSSQL and Tomcat)Thank you. Low-Code App Development System Administration ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Moderation Team has archived post 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 agoramau Cognizant Technology Limited replied to PradeepPydiHi, During the server recycle you can truncate the lock table and try. Posted: 1 year agoPradeepPydi Anthem replied to ramauTable size is not an issue and not recommended to truncate PR_SYS_LOCKS table. Posted: 1 year agoAbhinav7 PEGA replied to PradeepPydiHi , Have you observed any database exception.It might be due to DB deadlock .Run below script. ALTER DATABASE <pegadb> SET READ_COMMITTED_SNAPSHOT ON; Thanks, Abhinav Posted: 1 year agoPradeepPydi Anthem replied to Abhinav7We have this READ_COMMITTED_SNAPSHOT setting enabled long time ago.