SQL ISNT RESPONDING

Question

SQL ISNT RESPONDING

Maninder Karjee 0

I USE SSMS

SO IN SQL THE PREVIOUS QUERIES GET EXECUTED ALSO THE NEW ONES TOO . BUT WHEN I MODIFY THE PREVIOUS QUERIES THE RESULT REMAINS THE OLD SAME .THEN AFTER THE FEW TIME PERIOD THE SAME PROBLEM HAPPENS TO THE NEW QUERIES THAT I EXECUTED.

EVEN AFTER MANY SAVE AND REFRESH ,THE RESULT IS STILL SAME.

Erland Sommarskog 136.7K Reputation points MVP Volunteer Moderator

2026-08-22T12:50:30.92+00:00

I am not sure I understand. Your title suggests that SQL Server is not responding, but your text says that queries are executed. And then you seems to be saying that when you change the queries, you get the same result as before - which sounds very strange.

Could you describe more closely what you are doing? Would it be possible to record a short video that demonstrates the issue?

1 answer

Your answer

Erland Sommarskog 136.7K Reputation points MVP Volunteer Moderator

2026-08-22T12:50:30.92+00:00

I am not sure I understand. Your title suggests that SQL Server is not responding, but your text says that queries are executed. And then you seems to be saying that when you change the queries, you get the same result as before - which sounds very strange.

Could you describe more closely what you are doing? Would it be possible to record a short video that demonstrates the issue?

Answer 1

If you have multiple queries written in the same query window, SSMS will execute all of them from top to bottom every time you click "Execute" (or press F5).

The Fix: Use your mouse to click and drag to highlight (select) only the specific query you want to run. When you click Execute, SSMS will only run that highlighted text.

If your old results are stuck on the screen and never changing, SSMS might be configured to stop sending new results to your grid.

The Fix: Go to the top menu and select Query > Query Options. Look under Results > Grid and make sure the box for "Discard results after execution" is unchecked.

Sometimes the SSMS user interface grid gets visually "stuck" and stops rendering the updated data, even though the database is processing it.

The Fix: Completely close your current query tab (save it first if you need to). Open a brand new query window (Ctrl + N), paste your modified query there, and press F5. This forces SSMS to open a fresh results grid.4. Check for uncommitted transactions (BEGIN TRAN)If you previously ran a query that started with BEGIN TRANSACTION but you never ran COMMIT, your session is locked into a temporary snapshot of the data.The Fix: Open a new query window, type ROLLBACK; and execute it. Then try running your modified query again.