This is a must for me as well. And just to be clear, when I close down other instances of SSMS and only have one, SSC still thinks I have multiple instances open, so I have to close every instance just to get it to refresh itself and work with the one instance.

I'd like to see this feature. It's not that you can't have one SSMS instance connect to multiple servers, you can. However from a "safety" perspective I try to have different servers in different instances so that I don't accidently modify one server by executing commands in one instance. It's also nice to organize work by having different projects in different windows.

At a minimum you shoudl have some way to force SSC to re-check that you really do have multiple SSMS instances open before it refuses to load because I have only one open and it keeps telling me I have multiple. I now must close everything I have open so I can close all instances of SSMS and then re-launch SSMS just so SSC will recognize that only 1 copy is truely open.

This would be neat as myself and most of my team members tend to use several instances of SSMS.

I have to second HLee. This feature is a must for us to be able to proceed. We follow the same practices as HLee explained....different instances of SSMS to keep it straight which server we are working on. It is rare for me to only have one instance open at a time.

In the same vein as JoeFJ:

Personally I believe that simply adding either an additional check at the time when I choose Open from Object Explorer or choose SQL Source Control from the Tools menu, or that the check for running instances be moved to that point, instead of at Query Analyzer start. May do the trick.

This is a must for us as well. We all have multiple monitors and as a rule we use a different instance of SSMS for each server we are connected to. This avoids the confusion and chaos that can ensue when you are working in different environments/servers with the same code in the same instance of SSMS

I agree multiple instances of SSMS should be supported. However, I can accept not having multiple SSMS instances with open SQL Source Control tabs. But, I should be able to have multiple SSMS instances open if only one of them has SQL Source Control open.

We also utilize multiple SSMS as a method to easily differentiate environments / locations. Additionally it is handy when working a particular issue or project with dozens of tabs in use to just open a new SSMS. This way you don't lose your place in the original work.

Absolutely agree, it is must. I always have opened two SSMS, one for production, one for development.

Hi Marty,

You can use 1 SSMS to connect to 2 different servers. Would that work for you?

It is almost a must have feature for our shop. We work on 2 different servers daily.

Would be most useful for people who have to work on different projects / databases / servers side by side.