Hi @KyleKataan ,
We have several cubes running on our instance. We had the issue when 1 processing job entering the instance locking phase, a second job on a different cube failed with "lock conflict". Is there a server property which controls the timeout?
Please check the action plan Proposed Remedies for locking conflict between processing jobs in below article:
https://learn.microsoft.com/en-gb/archive/blogs/jason_howell/analysis-services-stops-accepting-new-connections-processing-commit-locks-hurt
I am able to manually lock a database via xmla. Is there a possibility to manually simulate a lock on instance level?
Please check the MDX script below:
BEGIN TRAN
GO
<Lock xmlns=”http://schemas.microsoft.com/analysisservices/2003/engine”>
<ID>496CEC1F-D66A-4C80-9E14-305D6CF41D86</ID>
<Mode>CommitExclusive</Mode>
</Lock>
You can find more detailed information in below blog:
https://blog.calvett.co.uk/2009/09/23/enter-the-ssas-server-level-lock/
You may also refer to this blog https://blog.crossjoin.co.uk/2017/03/18/ssas-2016-locking-improvements/
Regards,
Zoe
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.