How can we help you today? How can we help you today?

SQL Source Control Multiple Instances

I have the setting set to allow SQL Source Control to open in multiple instances. Even when I have verified that I don't have SQL Source Control selected for a specific database (let's call it 'database x') is telling me that database x is selected in another window. I can't seem to figure out how to identify which of the 6 instances of SSMS is the one that SOC thinks has database x selected. Is there any way to identify this? It seems like the error should be able to be more specific about which instance SOC thinks has the database selected. Could it at least report the PID that SOC thinks is selected? The other strange thing is that I went into each of the 6 instances I have open and specifically selected a completely different database and pulled up the SOC window for that database, so there is no reason SOC should think I have 'database x' selected because I have specifically pulled up the SOC window for a non-'database x' database.

The only way I have resolved this in the past is if I close out of each of my instances completely. That is a hassle because while SQL Prompt will restore all of my tabs, it restores them all in the first instance of SSMS that I open. So I have to go through and sort out which instances should have which tabs. It would be great if SQL Prompt would be aware of which tabs were opened within a specific instance so that when I opened SSMS again it would restore the tabs within separate instances as well. That's a whole separate request though.
adam_hafner
0

Comments

5 comments

  • way0utwest
    Adam,

    I'm not sure there's an easy way to enhance SOC here. Even if we could identify the instance, likely we'd just give to a PID, which you'd have to trace to an instance.

    In your description, I'm assuming that in one instance of SSMS, the plug in reports that you have a database deleted? Is that correct? Your use of "it" is a little confusing.
    way0utwest
    0
  • adam_hafner
    @way0utwest , sorry for not being clearer. I did however enter this issue as a support ticket and found out that this issue is actually a bug with SOC and SSMS 17. Apparently when you deselect a database that is linked in SOC it doesn't release it from all the other instances and it just remains locked. Jessica Ramos is escalating it to Development to address the issue.

    I would say, even the PID would be a great benefit, it is at least *something* you can attempt to track down and resolve the issue. Right now you are just stuck fumbling around until you find the offending instance.
    adam_hafner
    0
  • way0utwest
    Thanks, and I'll see if I Can get someone to work on this. Maybe getting the PID is a good idea.

    I've never used mutliple SSMS instances, and I'm sure you have a good reason, but I don't know that a lot of people have this pattern of working. Is this to separate work by instance or project?
    way0utwest
    0
  • adam_hafner
    Thanks @way0utwest!

    Yes, the projects are broken up into environments and in one environment I might be in one phase and in another environment I might be in another phase. I could keep everything in one instance and use tab coloring, but I would have so many tabs open that it becomes a mess to keep organized. There are at least 4-5 different suggestions that have been posted in SQL Prompt's UserVoice, but none of them appear to be getting much attention from Red Gate.

    https://redgate.uservoice.com/forums/94413-sql-prompt/suggestions/5724478-improved-tab-navigation
    https://redgate.uservoice.com/forums/94413-sql-prompt/suggestions/1773091-better-tab-management
    https://redgate.uservoice.com/forums/94413-sql-prompt/suggestions/13969344-show-part-of-the-sql-text-on-the-tabs-hint
    https://redgate.uservoice.com/forums/94413-sql-prompt/suggestions/6681088-rename-open-tabs
    https://redgate.uservoice.com/forums/94413-sql-prompt/suggestions/6711656-query-tab-naming

    I am sure I am missing some...lol =) . I know Red Gate is definitely busy, but it would be great to see something done about tab management.

    I know there are some ways to customize the tabs in SSMS as well, but its not nearly as flexible as it should be. I have also used SSMS's Solution Explorer but for some reason Solution Explorer in SSMS is not working like it used to. Even when it did, it would just list the ambiguous script file name which was generic (SQLQuery4.sql, etc) unless you took the time to save the file to a meaningful name. Which was kinda silly to do since they are really temporary in most cases.

    Sorry, I kinda went on a rant...I'll get off my soapbox now. :D
    adam_hafner
    0
  • way0utwest
    Thanks, and makes perfect sense. That's a good list of things that would be helpful.

    I'll vote some up and make some noise. No promises, but I'll try.
    way0utwest
    0

Add comment

Please sign in to leave a comment.