---
id: post/duiliotacconi-com/2074
type: post
title: Use sqlServerSessionId to spot on blocking sessions in Dynamics 365 Business Central 2026 Wave 1
summary: Business Central 2026 Wave 1 (v28) adds sqlServerSessionId to Long Running Queries telemetry (RT0005) and other signals that carry a SQL statement. When a Lock Snapshot (RT0013) shows a blocking SQL session without an AL stack trace because the blocker ran on another service tier, this ID can be traced through RT0005 to find the offending AL session and method.
tier: community
language: en
tags:
  - telemetry
  - lock timeouts
  - performance
  - blocking sessions
  - sql sessions
  - multitenant
  - debugging
system: platform
review:
  state: reviewed
  by: opus
  at: "2026-10-08T01:54:07.850Z"
  flags: []
generated:
  at: "2026-10-08T01:26:53.141Z"
  pipeline: 0.2.0
  prompts:
    extract-post: 1
  input_hash: 81d53472b0c0076e11d599cb4f6e06bc950945a219147139517a389cc1ece304
evidence:
  - kind: blog
    url: https://duiliotacconi.com/2026/07/22/use-sqlserversessionid-to-spot-on-blocking-sessions-in-dynamics-365-business-central-2026-wave-1/
    title: Use sqlServerSessionId to spot on blocking sessions in Dynamics 365 Business Central 2026 Wave 1
    date: "2026-07-22"
    commit: null
    t: null
    quote: null
links:
  learn: []
  objects: []
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
post_id: "2074"
source_id: duiliotacconi-com
source_name: Duilio Tacconi
url: https://duiliotacconi.com/2026/07/22/use-sqlserversessionid-to-spot-on-blocking-sessions-in-dynamics-365-business-central-2026-wave-1/
published_at: "2026-07-22T13:51:07.000Z"
author: Duilio Tacconi
full_text: false
words: 1071
quotes: []
code_objects_mentioned:
  - codeunit 54001
  - query 54010
systems:
  - platform
  - development
versions_mentioned:
  - 2026 Wave 1
  - v28
preview:
  embeddable: true
  frame_url: https://duiliotacconi.com/2026/07/22/use-sqlserversessionid-to-spot-on-blocking-sessions-in-dynamics-365-business-central-2026-wave-1/embed/
  image: https://i0.wp.com/duiliotacconi.com/wp-content/uploads/2026/07/lrq.png?fit=1200%2C503&ssl=1
  image_alt: null
  image_w: 1200
  image_h: 503
  site_name: Dynamics 365 Business Central tales, myths, legends. And something serious.
  favicon: https://duiliotacconi.com/wp-content/uploads/2023/07/cropped-wordpress.png?w=32
  probed_at: "2026-10-07T11:50:13.899Z"
---

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

[Read the post](https://duiliotacconi.com/2026/07/22/use-sqlserversessionid-to-spot-on-blocking-sessions-in-dynamics-365-business-central-2026-wave-1/) · Duilio Tacconi (Duilio Tacconi, MVP) · 2026-07-22 · 1071 words · tier community · reviewed (checked by Opus)

> Business Central 2026 Wave 1 (v28) adds sqlServerSessionId to Long Running Queries telemetry (RT0005) and other signals that carry a SQL statement. When a Lock Snapshot (RT0013) shows a blocking SQL session without an AL stack trace because the blocker ran on another service tier, this ID can be traced through RT0005 to find the offending AL session and method.

## Key points

- sqlServerSessionId is now included in all telemetry traces containing sqlStatement values, making it possible to correlate lock timeouts across NSTs
- Lock Snapshot signals (RT0013) cannot provide AL Stack Trace for blocking sessions running on separate NSTs, creating a gap that sqlServerSessionId helps fill
- Investigation workflow involves isolating lock timeouts, filtering lock snapshots for the blocking sqlServerSessionId, then finding Long Running Queries with that same ID
- Concurrency issues can be resolved with ReadIsolation(IsolationLevel::ReadUncommitted) or by optimizing queries using AL Query objects with proper joins and aggregations

## AL objects mentioned

As named in the post. A name that matches one object page by exact type and name links to it; the others stay as named.

- codeunit "54001"
- query "54010"

Not found in BC28-30: codeunit "54001", query "54010".

## Context

- Features: sqlServerSessionId in telemetry, Long Running Queries signal (RT0005), Lock Snapshot signal (RT0013), Lock Timeout signal (RT0012), ReadIsolation levels, AL Query optimization
- Versions: 2026 Wave 1, v28

Source: Duilio Tacconi, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.