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

 

[The_Doc_Man]

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 the brief exchange between me and GPGeorge regarding launching a Windows App.

One factor to consider: Classic Outlook is one of the few apps for which I know this answer explicitly. There will always and only be either zero or one instances of Outlook open on a single machine because of the way Outlook sharing is defined. For contrast, see Word, Excel, or PowerPoint. In the case of Outlook, it is the .PST files that are being shared. In the case of Excel, Word, or PowerPoint, you cannot have two sessions working to modify the same target file at the same time.

What happens when you open Classic Outlook? The sequence includes a test for an existing instance, and if one exists, you get linked to it. It is the moral equivalent of late-binding in Access, where the app opens with no tables linked and after some introspection, dynamically links to the tables.

In the case of SSMS, I don't specifically know what file types are being shared, but it appears clear by your assertion of "new session" of SSMS. The fact of sharing that DB is not part of the choice of how many sessions can be open. Therefore, you get that new session.

Part of this is the structure of the app itself. MANY (like, most all) apps from Microsoft have a "pure code" segment and a "data area" segment of memory. They are written to allow some memory management magic to occur so that there is only one copy of the program's code but potentially many copies of the data area. One code segment per system, one data segment per user session for that program. The magic of memory management thus allows you to not have 3 or 4 copies of the pure-code section, thus saving memory requirements. (Without this feature, Windows would be an even bigger memory hog than it already is.)

UPDATE EDIT: When launching an Access file, you can INDEED have multiple copies of MSAccess.EXE - but there will always and only be one copy of any of the .ACCDB or related files.

 

[Isaac]

have you noticed that the later versions of excel make it more difficult to deliberately open two instances of excel? still posible, but more difficult

 

[GPGeorge]

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

And I assume that your IT has also designated the version of SSMS you currently use (19, 20, 21, 22?) as the default app to open .SQL files?

 

[dalski]

Not bringing anything new here but commenting for moral support - double-clicking - mine opens in an existing instance (ver-22; but obv's due to file type assignment in Windows). I'm not experienced enough in SSMS to confirm if I've encountered a fresh instance of an application being launched when opening the associated filetype from Windows. I would state that this is the default behaviour of most apps I've encountered.

 

[Albert D. Kallal]

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

We probably could/should have started a new thread on this issue.

And, not knowing what been attempted so far?

Well, the "hammer" and chew up your time? Well, one could re-install, or even attempt a "repair".
I most certainly noticed during the install, at one point in time one is asked if you want to "associate" the .sql file extension with SSMS.
(this thus suggests a re-install, as the "repair" option does not offer to associate the .sql extension, but installing does).


And, another idea? Right click on the .sql file, and choose "open with"

(now, as above shows - I have 3 versions installed).

So, you then get this - and can choose SSMS 20.

As noted, I much suspect you done the above a zillion times, but
it's still a FYI for others here to try.

Also, keep in mind that if you running SSMS as admin, then a 2nd copy is always launched.
(this is because the windows UI can't hand off the file clicked on to another process running with "admin" rights, so, another copy is launched).
Again, above is well known, but a FYI for everyone here.

And the noted fix if above all does not work?
Check the registry for if DDE settings exist, this one:

HKEY_CLASSES_ROOT\sqlfile\shell\open\ddeexec

And of course, Visual Studio, Azure Data Studio, and even Notepad++ with SQL plugin's can all hi-jack the .sql extension....
(so, if ANY of these are installed AFTER SSMS, then again it can/will often break).

And, you can actually test/check if this is SSMS, or the windows file extension issue.

While SSMS is open? You can drag the .sql file into the SSMS window - if that works, then dde settings etc. are ok, but the .sql file assocation is messed up.

R
Albert