Applies to Product -Dynamics 365 Lifecycle Services
What’s happening?
A large SQL blocking chain was observed, causing performance issues in the application. The customer requested assistance in matching the AX processes to the SQL blocking SPIDs.
Reason:
The head blocker was identified as being caused by a custom query running on the system, specifically involving custom components related to various Dynamics AX modules. This was linked to the use of temporary tables in the custom code, which contributed to the blocking behavior.
Resolution:
What’s happening?
A large SQL blocking chain was observed, causing performance issues in the application. The customer requested assistance in matching the AX processes to the SQL blocking SPIDs.
Reason:
The head blocker was identified as being caused by a custom query running on the system, specifically involving custom components related to various Dynamics AX modules. This was linked to the use of temporary tables in the custom code, which contributed to the blocking behavior.
Resolution:
- Analyze the telemetry data to identify the blocking issue and the relevant processes involved.
- Review the call stack associated with the blocking chain to pinpoint the specific custom queries causing the issue.
- Recommend revising the custom code to avoid using temporary tables, which could improve performance and prevent similar blocking issues in the future.
- Inform the customer that further development or in-depth analysis may fall outside the scope of standard support and may require advisory services.
- Suggest exporting the production environment to a UAT environment for further analysis if direct access to production is not possible. This would allow for viewing locks in sys.dm_tran_locks to better understand the blocking behavior.
- Clarify that the support team can assist with actual issues encountered in the application but proactive checks without a specific issue may not be covered under standard support.