April 5, 2007 at 11:54 am
The biggest problem (well, distraction from productivity) I've had to date with SQL 2005 was with how ctrl+tab works in SSMS.
In SQL 2000's Query Analyzer, if you had several windows open, pressing ctrl+tab would move the current window to the bottom of the stack and activate the now-topmost window.
In SSMS under the same situation, hitting ctrl+tab opens a dialog that lists the first 15-20 characters of each file name, including the drive and path... and since I don't store my files in (or set my default folder to) the root folder, the actual file name is not displayed -- which for 80% of my windows would just say "Query##" anyway. Hit and release ctrl+tab once, and the topmost window is moved "down" one, exchanging places with the second-from-the-top window... which is not too useful if you have three or four winows, let alone 10, let alone a window that is behind the top two or three.
But I found a workaround, posted by "ayeltsov" on Microsoft's SQL Server 2005 feedback page. Here it is:
Looking at the VS commands, I see there are 2 types of switching:
"Next Document Window" and "Next Document Window Nav".
Could the matter be in simple binding to a different command?
UPDATE:
I have haceked this to work. in <C:\Users\USERNAME\Documents\SQL Server Management Studio\Settings\CurrentSettings-2005-11-03.vssettings> file, replaced
<UserShortcuts/>
with
<UserShortcuts><RemoveShortcut Command="Window.NextDocumentWindowNav" Scope="Global">Ctrl+Tab</RemoveShortcut><Shortcut Command="Window.NextDocumentWindow" Scope="Global">Ctrl+Tab</Shortcut><Shortcut Command="Window.NextDocumentWindow" Scope="Query Designer">Ctrl+Tab</Shortcut></UserShortcuts>
and I'm enjoying the useful behavior of ALT+TAB.
This works. Two things: on my box the file was under "C:\Documents and Settings\<MyLogin>\My Documents\SQL Server Management Studio\Settings"; and you have to hold down ctrl while you hit tab to cycle through the windows. Now if only SSMS worked and ran as fast as Query Analyzer...
Oh, and just to mention, I'm not being entirely altruistic. This is darn abstract stuff, and I know I'll lose it or it. But by posting on SQL Server, I'll always know where it is. [Thanks Maude!]
Philip
Viewing post 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy