Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2022 Release Wave 1 PlanDynamics 365 release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.
2022 release wave 1 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
In CRM 2013, when assigning a record (changing owner), we experienced serious performance problems. The asynchronous service runs several update queries. The first update query takes appr. 11 seconds. The following updates are probably fast; however, they finish with exact delays of 10.00 seconds each. It means the whole process lasts for more than a minute (img 1).
Why there are 10 seconds delay between the steps? Is there a way how to remove these delays? We need them to run immediately and not to slow down other operations.
If some query comes to DB in that time, it is blocked for a long time. In this case 68 seconds (img. 2). Often, the problem lasts for several minutes (img. 3).
Have you tried accessing the SQL Server and running the queries there and see if the execution plan helps you create some indexes in order to reduce the Query Execution Time?
Hi Francisco, Thanks for your feedback. However, we don’t deal with database speed, but with delays of 10.00 seconds exact fixed length between queries.
These delays are most likely to do with the cascade assign rules. By default, re-assigning an account will cause all related contacts/activities/opportunities etc. to be re-assigned as well and usually this isn't desirable. Doing this cascade has a big impact on security as well which can really slow things down.
Check the cascade rules on the relationship between account and related records - see blogs.msdn.com/.../check-and-set-assign-cascade-relationship-behavior-for-microsoft-crm.aspx
Also - msdn.microsoft.com/.../gg309412.aspx;MSPPError=-2147217396
Hope this helps
Hi Scott, Thanks for your feedback. We are aware of everything you have written. And the cascading rules are desirable for us in this case. However, single queries of the cascading process run with 10s delays. That means whole process can take several minutes and there is a DB lock for whole process. We’d like to remove these delays to shorten the process and the lock to a few seconds.
You will need to optimise the update process by either removing the cascade rules (probably not desirable since you'd need to implement some alternative batch process to do this) or optimise the updates of the cascaded entities. If there are plugins/realtime workflows that run on the updates of the child records then it will slow the whole process down.
A good resource is www.microsoft.com/.../confirmation.aspx and www.microsoft.com/.../details.aspx
Additional information: We realized that all the processes blocking the server with delays are in sleeping state. Why does it sleep when it blocks DB?
This will happen where there is another transaction that is blocking the sleeping one. That process is awaiting commit of another process. The other transaction could be an update that fires a plugin that is taking a long time. Check that you have no long running transactions - see my post on plugin execution monitoring - develop1.net/.../Monitor-Monitor-Monitor.aspx
We got some hint that it could be solved in newer version of CRM (better processing of Assign request). We upgraded to CRM 2016 and it is running without the performance problems for a month.
Business Applications communities