microsoft / microsoft/vscode-mssql

[Feature Request]: Top Operations tab for QUERY RESULTS

Open
#20,131 3 comments 0 reactions 0 assignees View on GitHub
Area - Query Plan Enhancement User-filed
Dominant language
TypeScript
Stars
1.9k
Forks
610
Avg merge
2d 3h
Merged PRs (30d)
97

Description

### Feature Description

With ADS retirement, it would be very useful to port the Top Operations tab over to VS Code to facilitate analysis of complex, multi-node execution plans.

### Problem and Motivation

With the less-than-intuitive "Find Node" feature currently in the mssql extension (side note: I think it needs a fair amount of debugging), it's nearly impossible to quickly zero-in on the most significant nodes on a large execution plan. Providing a Top Operations tab will allow immediate access to the most expensive nodes.

### Related Area

- [ ] Connection dialog
- [x] Query results panel
- [ ] Query editor
- [ ] Object Explorer
- [ ] Table Designer
- [ ] Schema Compare
- [ ] Schema Designer
- [ ] Local container
- [ ] GitHub Copilot integration
- [x] Query Plan Visualizer
- [ ] Other (please describe below)

### If you selected "Other", please describe the area

_No response_

### Confirmation

- [x] I have searched existing feature requests and couldn't find a match
- [ ] I want to help implement this feature

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the mssql extension's Query Results panel and Query Plan Visualizer, then compare the retired ADS Top Operations tab with the existing Find Node behavior. Done means a VS Code Top Operations tab that helps users quickly identify the most expensive nodes in complex, multi-node execution plans.

Written by the indexing model from the issue text.

Assessment

Tech stack
sql, typescript
Domain
database, devtools, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.