[Bug]: MSSQL extension hangs after query execution, blocking subsequent runs; requires "Reload Window"

[jsantos-iplus]

Description

After executing a T-SQL script—whether from an existing file or a "New Query" tab—the extension becomes completely unresponsive. This behavior is inconsistent in timing but persistent in occurrence. It affects all types of connections (Local, Azure, Remote VM) and happens regardless of how long the tab has been open.

Additional Context
The issue is not tied to a specific server or script complexity. It can happen immediately after the first execution or after several successful ones. Once the "hang" occurs, only a full window reload restores functionality, but the issue eventually recurs.

Steps to Reproduce

1. Connect to any SQL Server instance (Local or Cloud).
2. Execute any query (simple SELECT or complex script).
3. After execution finishes, attempt to run another query or interact with the SQL results/connection.

Observation: The extension "freezes." No further queries can be executed.
Current Workaround: Run F1 > Developer: Reload Window.

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

Extension Version: 1.40.0 (Latest)
VS Code Version: 1.109.5
OS: Windows 11
SQL Server: Various (Local, Cloud, Azure SQL)

Confirmation

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

[kburtram]

@aasimkhan30 this sounds similar to the issue we were discussing yesterday. Can you please try to confirm?

[jsantos-iplus]

This error has been happening for a long time, ever since I migrated from Azure Data Studio to VS Code when the announcement came out that it would be discontinued. Plus, this error didn't happen in Azure Data Studio.

[jsantos-iplus]

Below is a WeTransfer link with a video showing the issue. I'm sending it this way because I couldn't find a way to attach it while creating the report.

https://we.tl/t-JxVaCfS2Y5

[samgusick]

Happens all the time for me and my teammates! I've been trying to get my them to switch over from SSMS, but this is the biggest hurdle. I find that a full exit is usually more effective than reloading the window.

[jsantos-iplus]

Happens all the time for me and my teammates! I've been trying to get my them to switch over from SSMS, but this is the biggest hurdle. I find that a full exit is usually more effective than reloading the window.

Wow, I agree. I like SSMS (especially v22) because of how smooth it handles results, but I love how fast the VS Code extension is evolving—you can do so many cool things with it.

My teammates and I manage multiple massive databases, and we even use a custom extension I built to quickly script out objects for tweaks and improvements. Honestly, SSMS just doesn't offer that level of flexibility and flow right now.

I really wish this error could be fixed soon, because it's the only reason I've started looking into other IDE alternatives, like DataGrip.

[aasimkhan30]

I noticed this error in the video you shared. @samgusick and @jsantos-iplus do you see it every time the extension gets stuck?

If you can, could you also share the console logs from the DevTools?

Steps:

1. Help > Toggle Developer Tools
2. Go to the Console tab
3. Check for any existing errors
4. Try clicking Run again and see if any new errors appear
5. Copy/paste the console output (or share a screenshot) here

Also, if possible, it would help a great deal if you could collect and share the mssqltools logs as well:
https://github.com/microsoft/vscode-mssql/wiki/Collecting-MSSQL-Logs

From what you’re seeing, it looks like the backend process that powers the extension is crashing in your case. Which would also explain why the grid rows are coming back empty.
I am guessing other extension features like object explorer doesn't work as well when this happens

if you'd prefer, you can also email the logs to me aaskhan [at] microsoft [dot] com and reference this issue.

[FranBestinver]

Hi, guys.

I'm having the same freaking problem every day!

When is this bug going to be solved?

Thanks

[aasimkhan30]

@FranBestinver , can you please follow the steps in this comment and send me some logs ? #21361 (comment)

This is the highest-priority bug I’m targeting for the March release, and the logs will help a lot.