We're currently experiencing database locks on our one of our site collection's content database. These locks are generated by the SharePoint web server, and shows up in the Activity Monitor in MS SQL Studio as a 'SELECT' statement by our service account. It seems to occur through users using a heavily relied on list on the site collection. Nature of it will be that when users try save, it will hang, and then of course investigation reveals that there's a database lock blocking the 'INSERT' statements.
What I need to try do is identify which user on SharePoint, or what service, is generating this statement and causing the issue. Once it reaches the SQL database it just shows up as coming from the service account and web server, which makes it difficult to identify the true root.
I'm not a SharePoint administrator, and have limited experience. As a result, any help is truly appreciated.
Thanks.