microsoft / microsoft/vscode-mssql

[Feature Request]: Enable users to copy a connection URL to the database

Open
#20,267 1 comment 0 reactions 1 assignee View on GitHub

@Benjin is already working on this.

Since Jan 27, 2026.

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

Description

### Feature Description

Currently, users can share MSSQL database connection details by manually copying the connection string. However, there is no built-in UI feature in VSCode that allows users to generate and share a URI for this purpose. This request proposes adding a native option in the MSSQL extension UI to generate a URI that, when opened, launches VSCode and connects to the specified database.

Benefits:
- Streamlines collaboration by simplifying connection sharing.
- Reduces manual errors from copying connection strings.
- Aligns with existing URI-based workflows (e.g., Kusto).

### Problem and Motivation

A user wants to share a database connection with a colleague. Instead of copying and pasting the connection string, the user should be able to generate a URI like:
vscode://ms-mssql.mssql/connect?server=&database=&user=

Opening this URI should automatically launch VSCode with the MSSQL extension and connect using the provided parameters.

### Related Area

- [x] Connection dialog (SQL Server | Azure browse/Fabric browse)
- [ ] Query results panel
- [ ] Query editor
- [ ] Object Explorer
- [ ] Table Designer
- [ ] Schema Compare
- [ ] Schema Designer
- [ ] Local SQL Server Container provisioning
- [ ] SQL database in Fabric provisioning
- [ ] GitHub Copilot integration
- [ ] 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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.