Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

How to find a SSMS instance consuming the most of memory? Expand / Collapse
Author
Message
Posted Thursday, February 27, 2014 1:23 PM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Yesterday @ 9:00 AM
Points: 464, Visits: 1,533
I usually open multiple SSMS's in my PC, and at times when computer is running slowly, I check Windows Task Manager to find out who consumes the most in Processes tab. But how to relate it to my icon in TaskBar ? They all the same.
Post #1546104
Posted Friday, February 28, 2014 3:35 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Yesterday @ 10:40 AM
Points: 2,480, Visits: 3,023
Wouldn't it be easier to open connections to multiple SQL instances from one single SSMS? Each SSMS will need it's own resources, so opening up only one SSMS will perform better.

** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **
Post #1546240
Posted Friday, February 28, 2014 7:40 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Yesterday @ 9:00 AM
Points: 464, Visits: 1,533
Maybe it would be easier, but I have several servers: dev, test, UAT, prod. In order not to mix, I have one SSMS per server, with color-coded status panel in the buttom.

In this case it's easier, I think, to avoid a situation when you think you are in dev and running some delete or truncate and right after that you suddenly find that you are actually in production.

Post #1546342
Posted Friday, February 28, 2014 8:37 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Yesterday @ 10:40 AM
Points: 2,480, Visits: 3,023
I see your point although you can also colorcode the query-windows in SSMS. Register the instances in registered servers and apply a different color for each instance under the "connection properties" tab. If you connect through these registrations the query-windows will have a colored status bar.
If you want to look at resource-usage of each separate SSMS I don't think that can easily be done. Perhaps the "process explorer" from Sysinternals can give you a bit more insight.


** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **
Post #1546379
Posted Monday, March 3, 2014 6:16 AM
SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Yesterday @ 12:28 PM
Points: 4,611, Visits: 4,067
HanShi (2/28/2014)
I see your point although you can also colorcode the query-windows in SSMS. Register the instances in registered servers and apply a different color for each instance under the "connection properties" tab. If you connect through these registrations the query-windows will have a colored status bar.
If you want to look at resource-usage of each separate SSMS I don't think that can easily be done. Perhaps the "process explorer" from Sysinternals can give you a bit more insight.

If you aren't familiar with Process Explorer, I would highly recommend it. For your specific need, they have a "Find" icon you can drag onto a specific window and it'll tell you all about it. There's a level of detail there that you won't find in many other tools.

Also, HanShi is exactly right about the Connection Properties tab...Use custom color check box. You can specify any color you want.



Tally Tables - Performance Personified
String Splitting with True Performance
Best practices on how to ask questions
Post #1546891
Posted Wednesday, March 5, 2014 7:53 AM


SSCrazy Eights

SSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy Eights

Group: General Forum Members
Last Login: Thursday, December 4, 2014 7:52 AM
Points: 9,294, Visits: 9,495
Ed Wagner (3/3/2014)
[quote]
If you aren't familiar with Process Explorer, I would highly recommend it. For your specific need, they have a "Find" icon you can drag onto a specific window and it'll tell you all about it. There's a level of detail there that you won't find in many other tools.


They also have the reverse. For processes with windows (like SSMS) you can right-click on the offending process's line in Process Explorer, go to the "Window>" sub-menu and select "Bring to Front" to see which SSMS instance is the one taking so much memory.


-- RBarryYoung, (302)375-0451 blog: MovingSQL.com, Twitter: @RBarryYoung
Proactive Performance Solutions, Inc.
"Performance is our middle name."
Post #1547801
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse