Hello there, There is an annoying bug in the SSMS UI that I thought will be found and fixed with the latest version (19.0.1) I just installed. It persists in all the previous versions I used and is available here too. Here is the description: Connect to (LocalDB)\XXX SQL server, open a new query type "SELECT GETDATE()" and execute it. Connect to another SQL server ( i tested it with Azure one), open a new query type "SELECT GETDATE()" and execute it. try to change current Database by putting in the field (on the left of the Execute button) non-existing DB name ( I usually do this by miss-typing a correct name) and press enter. SSMS hangs up and shows "Not responding" no matter how much time you give it to just show error and returns control to you. After this the only way to use SSMS again is to kill it and start it anew. Hope you'll find the problem and fix it soon. Best regards, Hristo Serafimov

This is a know issue (if you are referring to the Azure DB scenario) that I've been investigating recently. There is no need to collect or share any dumps or repro: it's pretty obvious what the problem is. If the issue is about on-prem SQL, then I would like to hear more about it. I'll try the LocalDB scenario later today, but I would not expect it to be any different from the on-prem case, i.e. not repro for me.

I was able to repeat the issue, when connected to Azure with SSMS 19.0. The place to report bugs in SQL Server is here: https://feedback.azure.com/d365community/forum/04fe6ee0-3b25-ec11-b6e6-000d3a4f0da0 .

I am still seeing this issue when connecting to Azure SQL server. If I type in a database name that is either invalid, or do not have access to based on the currently logged in user, it hangs indefinitely after being unable to establish the connection. I am using SSMS 20: SQL Server Management Studio 20.0.70.0

Can't confirm, if I type a non-existing database name, I get immediatly the error message "Can't connect to".

Hristo Serafimov This was fixed in SSMS 19.1, and is also available in the current GA release, SSMS 19.2. Thanks.

SSMS UI bug (all versions so far)

Hristo Serafimov 35

Hello there,

There is an annoying bug in the SSMS UI that I thought will be found and fixed with the latest version (19.0.1) I just installed. It persists in all the previous versions I used and is available here too.

Here is the description:

Connect to (LocalDB)\XXX SQL server, open a new query type "SELECT GETDATE()" and execute it.
Connect to another SQL server ( i tested it with Azure one), open a new query type "SELECT GETDATE()" and execute it.
try to change current Database by putting in the field (on the left of the Execute button) non-existing DB name ( I usually do this by miss-typing a correct name) and press enter.
SSMS hangs up and shows "Not responding" no matter how much time you give it to just show error and returns control to you.

After this the only way to use SSMS again is to kill it and start it anew.

Hope you'll find the problem and fix it soon.

Best regards,

Hristo Serafimov

RatheeshKNair 6 Reputation points

2023-03-20T11:32:20.6633333+00:00

I tried to reproduce the issue and the moment I click the query window after giving invalid database name the DB name changes to master. Tried it on 12,14 & 15 versions of SSMS
Seeya Xi-MSFT 16,461 Reputation points

2023-03-21T06:11:11.6033333+00:00

Hi Hristo Serafimov,

Welcome to Microsoft Q&A!

I can't revert your situation because I don't have an Azure environment. I have added the corresponding tag for you.

Best regards,

Seeya
Hristo Serafimov 35 Reputation points

2023-03-21T11:27:06.9566667+00:00
It happens only on Azure connection I guess. Today I made new test with SSMS v.18.2.1 :

open SSMS and connect to Azure SQL.

select a DB and open new query window.

add 'asd' after the db name and press enter

after a while the message is shown (this is the output of the copy message action on the message form):
"TITLE: An error occurred while changing the current database.

Cannot open database "CentralClientasd" requested by the login. The login failed.

Login failed for user 'manusadmin'.

BUTTONS:

OK

"

after that the second message is shown:
TITLE: Microsoft SQL Server Management Studio

Invalid operation. The connection is closed. (System.Data)

BUTTONS:

OK

with details:

=================================== Invalid operation. The connection is closed. (System.Data) ------------------------------ Program Location: at System.Data.SqlClient.SqlConnection.GetOpenConnection() at System.Data.SqlClient.SqlConnection.get_ServerVersion() at Microsoft.SqlServer.Management.UI.VSIntegration.Editors.SqlScriptEditorControl.OnFillServerDBs(Object sender, CmdWithExtraParamsEventArgs a)

and the SSMS become unresponsive (see image)

undefined
Oury Ba-MSFT 17,791 Reputation points Microsoft Employee

2023-03-21T21:59:58.7866667+00:00

@Hristo Serafimov Thank you for reaching out.

I am sorry to hear about this issue. We would need to do some analysis using some back-end tool. I would suggest creating a support ticket. Please let us know if you don't have a support plan.

Regards,

Oury
Oury Ba-MSFT 17,791 Reputation points Microsoft Employee

2023-03-21T23:29:00.5766667+00:00

@Hristo Serafimov In addition to my comment above.

Please follow this do below to create a full memory dump of the SSMS process, using a tool like “procdump /ma” or a debugger. We will from our end can analyze the DMP file. For this you will also need to create a support ticket.

Get diagnostic data after a SQL Server Management Studio (SSMS) crash

Regards,

Oury
Oury Ba-MSFT 17,791 Reputation points Microsoft Employee

2023-03-21T23:29:24.81+00:00

@Hristo Serafimov Please let us know once the above are done.
MatteoT-MSFT 86 Reputation points

2023-03-22T02:10:06.8966667+00:00

No need to do that, unless you can repro this issue with on-prem or SqlLocalDB.
I have plenty of data around the Azure DB scenario (and I'm working on a fix already... though it's a little tricky)
Hunter Mayer 0 Reputation points

2024-03-29T23:12:23.8966667+00:00

I am glad this is allegedly fixed in the next version (I'll believe it when I see it. I'm on 19.1 now) I mess this up all the time when I am in a hurry. Remote DB's (azure lately) have been the previous connection before flubbing the name.
This has been working for me to recover (I really need to just update, but we're in the middle of a release... no system changes gonna happen anytime soon):
I can recover but its a pain (killing the app is fastest.) If patient you click on another open tab, wait. This gets you control back... eventually... patience required.The goal is to kill the query that was open when you typo'd the db name.
So Kill the open tab, if you have a solution open you can use the Solution Explorer context menu, it takes longer but ctrl+F4 will close. Alt tabbing out and bring focus seems to kick it a little more.

Got something you want to save. Ctr-A, (alt tab out and back to the hung app, wait... try again... etc.) Ctrl-x when the text is selected. When gone you know you got it. Leave it in the buffer or paste it somewhere based on your comfort levels. Then kill the query's tab. More times than not I'll get control back.
Hristo Serafimov 35 Reputation points

2024-04-12T12:55:49.1166667+00:00

Hi there,

Just downloaded latest version 20.1 and the problem is still there. This was the first thing I tested after download.

So please tell me if you need more information on the problem thou I think I described it well in the post and comments above.

Hope you will really find the problem and fix it.

Best regards,

Hristo Serafimov
Erland Sommarskog 106.5K Reputation points

2024-04-23T20:55:00.03+00:00

I can confirm - I tested in SSMS 20.1, and I guess I will need to kill it. I got a few error messages that I could click away, but apart from that SSMS is not responsive at all.
Oury Ba-MSFT 17,791 Reputation points Microsoft Employee

2024-04-25T00:14:52.4366667+00:00

@Hristo Serafimov

Could you please describe what the bug is?

Regards,

Oury
Erland Sommarskog 106.5K Reputation points

2024-04-25T06:48:34.87+00:00

Oury, Hristo has already done this. As I said, I was able to reproduce the scenario. Just try it yourself. But short: If you are connected to Azure SQL Database and type the name of a non-existing database in the Database dropdown and then press Enter, SSMS becomes unresponsive.
Oury Ba-MSFT 17,791 Reputation points Microsoft Employee

2024-04-26T22:24:43.5566667+00:00

Erland Sommarskog

Got it.! Our product group is aware of this issue. I will update in this thread once it is fixed.

Regards,

Oury
Sean Walsh 50 Reputation points

2024-07-18T12:19:23.1833333+00:00

This is such a horrible bug. I've just lost a huge query because I tried to switch databases and typed the name incorrectly.

If you leave the window open long enough eventually you get an error message like this:

So presumably there's a window that's supposed to be shown, which isn't, and then it hangs.

Accepted answer

MatteoT-MSFT 86 Reputation points

2023-03-22T02:06:15.5266667+00:00

This is a know issue (if you are referring to the Azure DB scenario) that I've been investigating recently.

There is no need to collect or share any dumps or repro: it's pretty obvious what the problem is.

If the issue is about on-prem SQL, then I would like to hear more about it.

I'll try the LocalDB scenario later today, but I would not expect it to be any different from the on-prem case, i.e. not repro for me.
Please sign in to rate this answer.

2 people found this answer helpful.
Hristo Serafimov 35 Reputation points

2023-03-22T16:25:49.2366667+00:00

No, it is about Azure DB indeed. I thought it has something to do with the 2 or more connected SQL servers but after that I proved it by testing it is only applicable for Azure DBs.

I guess it will be fixed soon.

Thanks in advance!

PS. probably one more thing can be fixed on this - when a certain Azure DB is selected the combo that shows selected DB contains only this DB and the master and in order to select another DB you should go to master (then combo is filled with all the databases available) and after that select another DB.

Edward Ahn 0 Reputation points

2023-06-06T22:49:51.88+00:00

It's been like this for years so I hope it'll be fixed!

Andrew 0 Reputation points

2023-12-05T18:39:19.69+00:00

Hi, any update on this being fixed? The Azure DB scenario happens 100% of the time that a non-existent DB name is used (always accidental). The query window becomes unresponsive but after 60 seconds or so it becomes partially responsive, it will take input with 10 seconds of input lag, staying frozen in the meantime. It's quite an annoying way to try to salvage what's in your query window before having to force close. Thanks!

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Oury Ba-MSFT 17,791 Reputation points Microsoft Employee

2023-12-19T18:42:11.04+00:00

Andrew this is fixed in SSMS 19.2 (latest GA release), originally in SSMS 19.1. Thanks.

Brent Long 1 Reputation point

2024-06-11T13:57:33.76+00:00

This is not fixed, as of the latest versions 19.2 or 20.1. Is anyone ever going to fix this? It's annoying and it's been around for YEARS. I know I'm not the only dev who's lost work and had to kill the SSMS process just because of a typo in the db name. Super frustrating, especially when you claim it's fixed.... I assume you fixed something, but it isn't this issue.

20.1 ------------------------------------------

SQL Server Management Studio 20.1.10.0

SQL Server Management Objects (SMO) 17.100.31.0+ccc8de5aee492d8b603963ce96e9f9877a21afa4

Microsoft T-SQL Parser 17.2.1.1+f4dfdb798c9aaa90bbe9a0cbfd92e100200ad26c.f4dfdb798c9aaa90bbe9a0cbfd92e100200ad26c

Microsoft Analysis Services Client Tools 20.0.3.0

Microsoft Data SqlClient (MDS) 5.1.5

Microsoft SQL Server Data-Tier Application Framework (DacFX) 162.2.111.2+1a4d708fee9d82fe4e01e02f3962d1e83d374807.1a4d708fee9d82fe4e01e02f3962d1e83d374807

Microsoft .NET Framework 4.0.30319.42000

Operating System 10.0.22631

19.2 ------------------------------------------

SQL Server Management Studio 19.2.56.2

SQL Server Management Objects (SMO) 16.200.48050.0+9bd30730a8cbcdac9d9788ba6605f3dda96e6b89

Microsoft T-SQL Parser 17.0.23.0+0d40faadb307b5d5fe930d64f47d2285ed3d0831

Microsoft Analysis Services Client Tools 16.0.20054.0

Microsoft Data Access Components (MDAC) 10.0.22621.3593

Microsoft MSXML 3.0 6.0

Microsoft .NET Framework 4.0.30319.42000

Operating System 10.0.22631

Erin Stellato 631 Reputation points Microsoft Employee

2024-06-19T19:34:48.3666667+00:00

Brent Long, Erland Sommarskog, Hristo Serafimov, Hunter Mayer

Acknowledging that this still occurs in SSMS 20.1. We had made changes in 19.2 but there's likely another code path that was not covered.

We have a work item for this and it's something we will address in SSMS 21.

Can you help me understand the scenario where you manually type in the database name, versus selecting it from the drop down? This is a "why is that your workflow" question - I'm aware that there are numerous ways to accomplish the same task in SSMS. Thanks!
Sign in to comment

4 additional answers

Erland Sommarskog 106.5K Reputation points

2023-03-21T21:36:53.5533333+00:00

I was able to repeat the issue, when connected to Azure with SSMS 19.0.

The place to report bugs in SQL Server is here: https://feedback.azure.com/d365community/forum/04fe6ee0-3b25-ec11-b6e6-000d3a4f0da0.
Please sign in to rate this answer.

1 person found this answer helpful.
Hristo Serafimov 35 Reputation points

2023-03-22T16:32:21.81+00:00

Sorry for the wrong place I chosen to place the problem, but this is the first site I found googling for related problem. Probably if I'd checked the SSMS menu Help \ Technical support I'd found the right place.

Thank you!

Erland Sommarskog 106.5K Reputation points

2023-03-22T18:57:24.5266667+00:00

Hey, it's alright to post about such things here! Postings here will not serve as bug reports, but you get a wider traction than posting to the feedback site. And in many cases, you may find yourself in the situation that you don't know if it is a bug, or something local to your machine. So sharing it here, and have other people to confirming the problem is absolutely a good idea. Then you can refer to the thread when you make the formal bug report.
Sign in to comment
Kyle Knapp 10 Reputation points

2024-06-20T18:28:22.7366667+00:00

I am still seeing this issue when connecting to Azure SQL server. If I type in a database name that is either invalid, or do not have access to based on the currently logged in user, it hangs indefinitely after being unable to establish the connection.

I am using SSMS 20:
SQL Server Management Studio 20.0.70.0
Please sign in to rate this answer.

1 person found this answer helpful.
Erin Stellato 631 Reputation points Microsoft Employee

2024-06-20T18:34:07.03+00:00

Kyle Knapp - copying comment from above (posted June 19, 2024):

Acknowledging that this still occurs in SSMS 20.1. We had made changes in 19.2 but there's likely another code path that was not covered.

We have a work item for this and it's something we will address in SSMS 21.

Can you help me understand the scenario where you manually type in the database name, versus selecting it from the drop down? This is a "why is that your workflow" question - I'm aware that there are numerous ways to accomplish the same task in SSMS. Thanks!

Kyle Knapp 10 Reputation points

2024-06-20T18:42:13.2333333+00:00

Thank you Erin, I didn't see that nested response.

For my workflow, we have Azure servers with hundreds of user databases, and unless connected to master, the dropdown only shows the currently connected DB (and master when logged in as admin). When logged in as admin, I can navigate between the dbs by typing/pasting their name. I primarily see issues when the db exists on a different SQL server (say EU instead of NA) and I am working from just a list of db names. If I paste a db name that either the server doesn't own, or the security context doesn't allow access to, then I am completely frozen until killing the ssms process.

Erin Stellato 631 Reputation points Microsoft Employee

2024-06-21T01:21:04.6333333+00:00

Kyle Knapp Thanks for the additional context, that's helpful. Would a temporary solution be to change the connection to connect to master, so you would have the drop down list of databases? Or there are too many servers/too many databases for that to help?

Erland Sommarskog 106.5K Reputation points

2024-06-21T08:51:26.4866667+00:00

Another workaround would be to right-click and select Change Connection from the context menu (and I have tied this command to a keyboard shortcut myself), and then select the database in the connection menu. But that does not help Kyle if he types the database name out of habit, and misspells it...

Erin, one thing to keep in mind is if the database is serverless and is paused. In that case, it will take some time before the connection completes anyway. It would be really nice is SSMS does not stall in this case, but you can move to another window to work with something else for a while.

Kyle Knapp 10 Reputation points

2024-06-21T09:16:29.4+00:00

I appreciate the suggestions! This isn't a large blocker in my workflow. It happens often enough that I decided to search for a resolution yesterday, and found this page. Seeing that this issue had been resolved in v19.2, I missed that it was already called out that it is a known issue in v20.

Erin Stellato 631 Reputation points Microsoft Employee

2024-06-21T13:38:26.3666667+00:00

Erland Sommarskog agree that serverless has its own behavior that can make interactions sluggish. Open to suggestions for how we don't "lose" users in that process - maybe some kind of visual to indicate that SSMS isn't hung up, just waiting.

Kyle Knapp Understood and glad you searched for the issue and commented. We do want to know when there are problems, so appreciate you taking the time to interact!
Sign in to comment
Olaf Helper 43,161 Reputation points

2023-03-20T09:56:25.8433333+00:00

Can't confirm, if I type a non-existing database name, I get immediatly the error message "Can't connect to".
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
Erin Stellato 631 Reputation points Microsoft Employee

2023-12-19T17:09:06.4233333+00:00

Hristo Serafimov This was fixed in SSMS 19.1, and is also available in the current GA release, SSMS 19.2. Thanks.
Please sign in to rate this answer.
Joris Stolwijk 5 Reputation points

2024-03-22T08:52:30.09+00:00

Hi, I just installed SSMS 20.0, but the issue is still present :(

Oury Ba-MSFT 17,791 Reputation points Microsoft Employee

2024-03-25T16:27:47.95+00:00

Joris Stolwijk

Did you install from https://video2.skills-academy.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-ver16.

What error message are you getting.?

Regards,

Oury
Sign in to comment

Share via

SSMS UI bug (all versions so far)

4 additional answers