December 12, 2013 at 7:04 am
I am having an exceedingly strange issue with SSMS. When opening new sql files (from explorer or file->open) or query windows (file -> new), if no change has been made in the active window, SSMS reuses the same tab instead of opening in a new one. This ONLY happens if the I attempt to open multiple scripts at one time or there is no change in the active tab.
So far I have tried just about every registry hack I could find using google, I have reinstalled SQL Server Management Studio twice now, update to the latest service packs, looked through the configuration options in SSMS and have yet to be able to solve this. My coworkers, using the same windows image, are NOT having this problem and they have used the same installation process. The only difference on my system was that visual studio 2008 was installed AFTER installing Sql Server, which caused its own host of other problems, but after removing VS, .Net Frameworks, and SSMS and reinstalling in the correct order those issues appear to be corrected.
I am running SQL Server 2008 Service Pack 3 10.00.5500.00 on windows 7 enterprise.
Any help anyone can provide would go a long way toward making today a less then frustrating experience.
Many thanks,
Wes
December 12, 2013 at 8:28 am
Not sure this post will make your day any easier, but here goes...
You might want to try and build a TEST workstation fresh from the image and install in the correct order, and see if that workstation has the same issue. If not, you transfer your files and transfer only non-SQL Server and non-SSMS settings to that new workstation. That would prove that it's likely a registry issue, although it won't prove exactly what that issue is..
If you really want to spend some serious extra time, you could then choose to compare the registries from the two machines, and maybe you find it, maybe you don't.... It could also be a corruption problem in the registry and sometimes, there's no finding that kind of problem.
The one advantage of this way forward is that you either discover that it's a bug, or that a fresh build solves it. Painful, perhaps, but cleansing....
Let me know how you make out...
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
December 13, 2013 at 6:37 am
Thanks for the reply, I was hoping more for someone else who has been through this, but alas I stand alone. It is a corporate machine at one of my client sites, so I will just have to have them re-image it and try the installations again. It does make me feel a bit better to know that whatever caused the issue is a mystery to the rest of the community as well though 😀
Wes
December 13, 2013 at 7:57 am
Well, I am a glutton for punishment and I just couldn't let something so silly ride and after thinkning about it the re-image would take just about forever since I have a lot of data that would need to be moved... blah blah blah, etc etc etc.
So after poking around, I found that there is an option in Visual Studio that creates precisely this behavior ("reuse current document window if saved") under Tools->Options->General->Documents, but this is noticeably absent SSMS 2008 (though it exists in 2012). I figure if I can find that registry key and add it to the SSMS configuration, it should work, but after playing around I could not find what registry key this alters. I will do some digging and report back what I find.
December 13, 2013 at 12:23 pm
Wesley Middendorff (12/13/2013)
Well, I am a glutton for punishment and I just couldn't let something so silly ride and after thinkning about it the re-image would take just about forever since I have a lot of data that would need to be moved... blah blah blah, etc etc etc.So after poking around, I found that there is an option in Visual Studio that creates precisely this behavior ("reuse current document window if saved") under Tools->Options->General->Documents, but this is noticeably absent SSMS 2008 (though it exists in 2012). I figure if I can find that registry key and add it to the SSMS configuration, it should work, but after playing around I could not find what registry key this alters. I will do some digging and report back what I find.
Did you change the setting in Visual Studio? There's some overlap between Visual Studio and SSMS when it comes to query windows and they may actually be using the same component.
Jason Wolfkill
December 13, 2013 at 5:55 pm
In my registry for SQL2012 I have the setting here:
HKEY_CURRENT_USER\Software\Microsoft\SQL Server Management Studio\11.0\General
It is a REG_DWORD value called ReuseActiveDocumentwindow.
You may have similar for SSMS 2008 with 10.0 instead of 11.0
MM
select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);December 16, 2013 at 8:55 am
That was it, thanks!
For SSMS 2008 the key is found at HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\100\Tools\Shell\General
Thanks for the help!
December 16, 2013 at 4:29 pm
Wesley Middendorff (12/16/2013)
That was it, thanks!For SSMS 2008 the key is found at HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\100\Tools\Shell\General
Thanks for the help!
Thanks for updating us with the actual location, always nice when that happens. Makes you wonder what else you can do via the registry doesn't it :hehe:
MM
select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);December 17, 2013 at 7:42 am
mister.magoo (12/16/2013)
Wesley Middendorff (12/16/2013)
That was it, thanks!For SSMS 2008 the key is found at HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\100\Tools\Shell\General
Thanks for the help!
Thanks for updating us with the actual location, always nice when that happens. Makes you wonder what else you can do via the registry doesn't it :hehe:
Just be sure to back up that registry before you start rummaging around in there!
Jason Wolfkill
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply