-
Notifications
You must be signed in to change notification settings - Fork 555
Description
Description
I'm working in a Dev Container but my MSSQL Extension is running on ui so I can login with my IT from the host system (Authentication type: Windows Authentication).
As long as I work with unsaved files I can execute queries. If I run a file stored in the container, it says it executed my query but it doesn't do anything.
Debug Output:
[6:35:40 AM] Started query execution for document "vscode-remote://dev-container+7b227...23a66616c73657d/workspaces/vws-server/scripts/vws/updsql/tmp/t.sql"
[6:35:41 AM] Finished query execution for document "vscode-remote://dev-container+7b227...23a66616c73657d/workspaces/vws-server/scripts/vws/updsql/tmp/t.sql"
Also if I try to save the output as a file, it doesn't know if it should work on the host filesystem or on the container filesystem - so it let's me select a file on the container but then does not write into it...
[7:08:04 AM] Started saving results to /workspaces/vws-server/scripts/vws/updsql/tmp/t.csv
[7:08:05 AM] Failed to save results. Failed to save t.csv: Could not find a part of the path 'C:\workspaces\vws-server\scripts\vws\updsql\tmp\t.csv'.
Steps to Reproduce
Run VSC with Dev Container and SQL-Server Plugin running on UI.
Execute Query from stored file.
No results are retrieved.
Affected Area
- Connection dialog (SQL Server | Azure browse/Fabric browse)
- 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 affected area
No response
Environment Information
VS Code Version: 1.107
MS SqlServer Plugin Version: 1.38.0
Host: Win11
Container: ALMA9
Confirmation
- I have searched existing issues and couldn't find a match
- I want to work on this issue