Solved SSMS22 Application Itself Slower Than SSMS21

[Albert D. Kallal]

Yes, I found plenty of similar people with same problem when googling the issue. Along with advice on how to 'fix'. Your verbiage in your response to me sounds dismissive and rude.
Maybe you have a different SSMS version? I only have one version installed. 20.2.37.0

Well, not my intention to be rude, if as such, then my apologies.

And really, this should be great news. And the reason?
Well, if everyone not having this issue, then that bodes well here - really, it does.

Since, if the issue not all that widespread?
It suggests that a fix is possible, right?

I mean, if EVERYONE had this issue, then really, no hope at all would exist until some fix is issued? Right?

So, my dismissing was in fact an attempt to bring hope to you and this post!

I stand by my position that it really is a good thing that not everyone is experiencing this issue...
(this may well not give you solace and some group hugs here,
but it means that the vast majority are not having this issue,
and that then means that some change should be possible here that will fix your issue)

So, you should see my post here as good news.....

have one version installed. 20.2.37.0

Ok, the title of this post was SSMS 22, and 21 -- but, you now talking about v20, then?
Version 20 suggests 2 versions of SSMS ago?

Based on title of this thread, I had to assume v22 or v21....
(probably would have been best to start a new thread
-- if you have a post on this issue already, then most happy to jump to that thread).

But, I assume that you are sticking to version 20, since 21 or 22 has your file click issue that then opens the 2nd copy of SSMS?

Or are you having this issue with version 20? (2 versions ago)?

So, it not clear what version you are talking about, since we have these
2 contradictory statements:

I only have one version installed. 20.2.37.0

--
since migrating to the newest SSMS, I can no longer double-click a .SQL file <---- but last version is 22, not v20??

Perhaps trying v22 would work? (if this is a possible choice, I would certainly try installing v22, or is this why you still on v20 then?)

I just checked my computer, and it turns out I have 20, 21, and 22 installed......
(and none of them had your issue, but after installing v22,
I most certainly did have to re-associate the .sql file extension, else it was launching v21, and it not 100% clear as to why even this occurred!!!).

R
Albert

 

[GPGeorge]

Thanks, Doc. That's the full explanation about why I made the observation I did, and why I highlighted the final phrase, "at that time". I was lazy and didn't bother to elaborate why that was so.

I think a previous post in this thread regarding opening the "wrong" version of SSMS can be explained by this phenomenon. If SSMS 21 was previously designated as the app to open .sql files, that's the app that will be used.

 

[Isaac]

I find that doubling-clicking on a file with the .sql extension opens it in the program with which that extension is associated at that time.

Me too. The question is whether it opens in the already-open instance of ssms or opens a new instance of ssms. for me it's doing the latter

 

[GPGeorge]

Me too. The question is whether it opens in the already-open instance of ssms or opens a new instance of ssms. for me it's doing the latter

see Posts 41 and 42.

 

[Isaac]

I wish I could try a different version just like that, but I'm unable to, our company IT department decides which version we will use on our virtual (vmware) desktop