microsoft / microsoft/vscode-mssql
[Bug]: Query Profiler UI overwhelmed on busy server
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 610
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 97
Description
### Description
- Attempting to launch query profiler when not connected to the server results in no UI feedback. Typically the user would expect a loading bar or spinner in the command pallete or status bar. Instead we get no feedback until the connection eventually succeeds/fails.
- Upon successfully launching a session, the status bar counter very quickly counts up from `0/0 events` to `/ events`, then hits `/10000 events` before dropping to `0/10000 events`.
- Start / Stop / Resume menu buttons are not responsive, require multiple clicks, or sometimes just never work.
- Column filters are unusable while the session is active. The popup closes on every data refresh.
- Column filters lost upon resuming a session. Stop > Update a column filter > Start. Note the column filter is removed.
- Quick filter lost upon resuming a session.
- Clear Data button does nothing. Data grid is not cleared or updated in any way upon click.
- Auto-scroll button does nothing.
This may just be due to connecting to a large/busy database and the UI being completely overwhelmed with data?
### Steps to Reproduce
1. Connect to a busy server
2. Right click a database and select Launch Query Profiler
3. Give the session a name
4. When the Query Profiler tab loads, notice that the UI is unresponsive and broken in many ways listed above
### Affected Area
- [ ] Connection dialog (SQL Server | Azure browse/Fabric browse)
- [ ] Query editor
- [ ] Query results panel
- [ ] Object Explorer
- [ ] GitHub Copilot integration
- [ ] Preview/Edit data
- [ ] Table Designer
- [ ] Schema Designer
- [ ] Schema Compare
- [ ] Local SQL Server Container provisioning
- [ ] SQL database in Fabric provisioning
- [ ] DACPAC/BACPAC export/import
- [ ] SQL Database projects
- [ ] Query Plan Visualizer
- [x] Other (please describe below)
### If you selected "Other", please describe the affected area
Query Profiler
### Environment Information
VS Code info:
```
Version: 1.137.0 (Universal)
Commit: 645f29cc3176500b4b5762ba887cf2a7f0ffdf2c
Date: 2026-09-08T13:43:59-07:00
Electron: 42.10.0
ElectronBuildId: 15109253
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
@github/copilot: 1.0.84.70.gdb75d0d
@github/copilot-sdk: 1.0.13-preview.4
OS: Darwin arm64 25.6.0
```
SQL Server extension info:
```
Installation
Identifier: ms-mssql.mssql
Version: 1.45.1
```
Connection info:
```
Microsoft SQL Server 2019 (RTM-CU32-GDR) (KB5102335) - 15.0.4480.2 (X64)
Jun 18 2026 17:54:32
Copyright (C) 2019 Microsoft Corporation
Developer Edition (64-bit) on Windows Server 2019 Standard 10.0 (Build 17763: ) (Hypervisor)
```
### Confirmation
- [x] I have searched existing issues and couldn't find a match
- [ ] I want to work on this issue
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the Query Profiler launch flow and UI for a session connected to a busy SQL Server, reproducing the listed status-bar, menu, filter, data-grid, and auto-scroll failures. Done means the profiler remains responsive and loading feedback, session controls, filters, clearing data, and auto-scroll work reliably during active and resumed sessions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql, typescript
- Domain
- databases, frontend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100