[Bug]: Query editor shows duplicate icons when MSSQL and PostgreSQL extensions are both installed

[croblesm]

Description

Describe the bug

When both the MSSQL and PostgreSQL extensions are installed in VS Code, the query editor displays duplicate action icons (e.g., Run, Explain, etc.)—one set from each extension. This clutters the UI and may confuse users, especially since some icons appear visually identical but may trigger different extension behaviors.

This likely stems from both extensions contributing similar editor/title actions without proper scoping or conditional logic based on the active connection type.

Screen.Recording.2025-06-05.at.9.50.41.AM.mov

Only the relevant set of icons for the active connection or query type should appear in the query editor. Extensions should scope their editor contributions to avoid duplicating UI elements when multiple extensions are present.

I also created this issue in the PG team repo:
microsoft/vscode-pgsql#67

Steps to Reproduce

1. Install both the MSSQL and PostgreSQL extensions in VS Code.
2. Open a SQL file or start a query editor for either MSSQL or PostgreSQL.
3. Observe the toolbar icons at the top of the editor.

Affected Area

• Connection dialog
• Query editor
• IntelliSense/auto-completion
• Query results panel
• Object Explorer
• Table Designer
• Schema Compare
• Schema Designer
• Query Plan Visualizer
• Other (please describe below)

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

No response

Environment Information

• VS Code Version: 1.100.3
• MSSQL Extension Version: 1.32.1

Confirmation

• I have searched existing issues and couldn't find a match
• I want to work on this issue

[markludlow]

@croblesm I ran into the same issue and I found a way to resolve this issue without changing the extensions. If you create a workspace for any mssql or postgressql project, you can disable any unwanted extensions specifically for that workspace.

This isn't as elegant as doing it automatically, but if the extension was automatically disables/hidden based on the type of database connection, and a user accidentally connects to the wrong type, they may lose the ability to connect to a different type of DB because the extension would be disabled/hidden. Also, the user would still see duplicate icons when they open the project and have not yet connected to a database.

I think manually disabling extensions per workspace gives the user full control over which database extension (or any extensions for that matter) to use, and is a better solution IMHO.

[vaverix]

Unfortunately that doesn't work for me, I use both databases in my company project. :(
We will move to one eventually, but we have both at this time.

[ocdi]

This bug is really frustrating, given the deprecation of Azure Data Studio. That handles both connection types really well, it is really frustrating to operate in vscode this way. I really want to get used to having vscode as my primary SQL interface but it is miles away from being ready.

[nikhilweee]

Completely agree. With Azure Data Studio deprecated there is no acceptable way to run mssql and pgsql together.