microsoft / microsoft/vscode-mssql

[Feature Request]: Show Profile Name instead of Server Name in footer

Open
#22,312 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area - Connection Enhancement User-filed
Dominant language
TypeScript
Stars
1.9k
Forks
610
Avg merge
2d 3h
Merged PRs (30d)
97

Description

### Feature Description

Show Profile Name instead of Server Name in footer

I usually use meaningful Profile Names as servernames are often crypric, particular if i work with fabric sql endpoint.

e.g.

🛠️Dev🟩
for SQL Endpoint abcdef123abcdef-o1zxzxzxzabsabsdev.datawarehouse.fabric.microsoft.com
🔬Test🟨
for SQL Endpoint abcdef123abcdef-a7zxzxzxzabsabstst.datawarehouse.fabric.microsoft.com
⚠️Prod 🟥‼️
for SQL Endpoint abcdef123abcdef-c3zxzxzxzabsabsprd.datawarehouse.fabric.microsoft.com

### Problem and Motivation

currently i see only the Servername which is the SQL Endpoint in the Footer, but in fabric those look very similar
(in sql server itself i would name my instances, but i can't in fabric)

worst case i change accidently change things in Prod...

### Related Area

- [ ] Connection dialog (SQL Server | Azure browse/Fabric browse)
- [x] 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
- [ ] 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
- [x] I want to help implement this feature

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.

Research direction

Start in the query editor area mentioned by the issue and trace where the footer displays the SQL server name and where the active profile name is available. Confirm how Fabric connections expose profile names, then update the footer so the profile name is shown and verify that Dev, Test, and Prod connections remain distinguishable.

Written by the indexing model from the issue text.

Assessment

Tech stack
sql, typescript, vscode
Domain
database, frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.