Dynamics 365 Business Central Online backend troubleshooting: what I am missing the most.

Dynamics 365 ERP - Development

The article discusses the challenges of working with Dynamics 365 Business Central SaaS compared to on-premises solutions, highlighting limitations in infrastructure changes and configuration settings.
The author emphasizes the importance of telemetry in identifying issues and making changes in the Dynamics 365 environment, particularly in relation to missing indexes and index advantages.
The post mentions the potential feature of disabling indexes for improved write performance and the need for related telemetry signals to monitor index usage.
The distinction between locking and blocking in database transactions is explained, with insights on controlling isolation levels and optimizing transaction duration.
The article addresses the detection and resolution of locks and blocks in Dynamics 365 Business Central online, highlighting the limitations of existing telemetry signals.
Deadlock scenarios are described in a simplified analogy involving fictional characters, followed by a more technical explanation of how SQL Server resolves deadlocks.
The author advocates for additional telemetry data on deadlocks, including information on the winning and rolled-back sessions, as well as the locked resources.
Lastly, the post discusses the challenge of resolving deadlocks in a high-concurrency environment, particularly in Dynamics 365 SaaS, and the importance of comprehensive telemetry for efficient troubleshooting.

Registered users can view the full text for FREE!