SSMS: Tabs should not change position unless I change them! - by Adam Machanic

Status : 

  External<br /><br />
		This item may be valid but belongs to an external system out of the direct control of this product team.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 265343 Comments
Status Closed Workarounds
Type Suggestion Repros 1
Opened 3/26/2007 11:25:41 AM
Duplicates 252881 Access Restriction Public


- If I open a new tab in SSMS, it should open on the RIGHT, not the LEFT.
- If I hit CTRL-TAB, focus should go to the next tab to the right.  It should NOT go back to the left, unless I hit CTRL-SHIFT-TAB.
- If I use the tab dropdown on the right, focus should shift to the tab I select.  The selected tab should NOT be moved to the leftmost position!
- If I open enough tabs that they won't all fit on the screen at once, an arrow (or arrows) should appear to help me navigate.  If there are offscreen tabs to the right, an arrow on the right should appear.  If there are offscreen tabs to the left, an arrow on the left should appear.  Then I can scroll back and forth.

Again, the most important thing here: tabs should NOT move, unless I drag them to a new position.  This is the most confusing aspect of working with SSMS.  You might think that the "third" tab is the query you're looking for, when in fact it has been moved around and is now some other tab entirely.  It makes for an incredibly frustrating user experience.
Sign in to post a comment.
Posted by Microsoft on 1/22/2008 at 10:50 AM
Hello - I'm not going to be able to get this in for SQL Srever 2008. This does not mean that the information is not relevant or valid; but we are not able at this time to work on this item. Note that this issue may also be fixed as a result of some framework issues we are dealing with.
Buck Woody, SQL Server Program Manager
Posted by Microsoft on 4/19/2007 at 3:09 AM
Hi Adam,

Thanks for reporting this issue. We shall considering fixing this in our future releases. Thanks again for being so descriptive.