Use sqlServerSessionId to spot on blocking sessions in Dynamics 365 Business Central 2026 Wave 1

Dynamics 365 Business Central 2026 Wave 1 (v28) Telemetry adds sqlServerSessionId in Long Running Queries (LRQ) signal RT0005. In practical terms, all the standard signals that are emitting a sqlStatement now also have the relatedsql server session id). Why sqlServerSessionId added in all traces that have sqlStatement != “” is important? Because, in Lock Timeout... Continue Reading →

Blocking session: the sharpshooter.

In SaaS, when moving from one cluster to another, an innocent token from an ISV app is renewed in a setup table. UPDATE "SQLDATABASE".dbo."CURRENTCOMPANY$EOS069_03 Sharepoint Setup$xxx" SET "Latest Token"=@0,"Token Expiration UTC"=@1,"$systemModifiedAt"=@2,"$systemModifiedBy"=@3 OUTPUT inserted."timestamp" WHERE ("Primary Key"=@4 AND "timestamp"=@5) Everything is fine. You are marching on your daily business and suddenly you see the lock timeout... Continue Reading →

Blog at WordPress.com.

Up ↑