microsoft / microsoft/vscode-mssql

[Bug]: Object Explorer does not label Columnstore Indexes correctly

Open
#22,713 6 comments 0 reactions 1 assignee View on GitHub

@aasimkhan30 is already working on this.

Since Aug 12, 2026.

Bug Triage: Needed User-filed
Dominant language
TypeScript
Stars
1.9k
Forks
610
Avg merge
2d 3h
Merged PRs (30d)
97

Description

### Description

**Describe the bug**
When creating a Clustered Columnstore Index (or Non-Clustered Columnstore Index), the Object Explorer in VS Code labels it as `(Non-Unique, Clustered)` instead of explicitly identifying it as a Columnstore index.

### Steps to Reproduce

**To Reproduce**
Steps to reproduce the behavior:
1. Run the following T-SQL to create a Columnstore Index:
`CREATE CLUSTERED COLUMNSTORE INDEX idx_test_CS ON dbo.TestTable;`
2. Refresh the Object Explorer and navigate to the Indexes folder for the table.
3. Observe the label for the index.
**Expected behavior**
The Object Explorer should indicate that the index is a Columnstore index (e.g., `(Clustered Columnstore)`), similar to how SSMS handles it.
**Screenshots**

Image

### Affected Area

- [ ] Connection dialog (SQL Server | Azure browse/Fabric browse)
- [ ] Query editor
- [ ] Query results panel
- [x] 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
- [ ] Other (please describe below)

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

_No response_

### Environment Information

- VS Code Version: 1.130.0
- MSSQL Extension Version: 1.44.1
- Operating System: macOS 26.5.2
- Connection Type : SQL Server

### Confirmation

- [x] I have searched existing issues and couldn't find a match
- [x] I want to work on this issue

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.