SSMS : Have new query window inherit certain properties from existing window

Welcome, guest Sign in | Your Profile | Help

HOME

YOUR DASHBOARD

CONNECTION DIRECTORY

SQL Server Home Downloads Feedback Surveys

SSMS : Have new query window inherit certain properties from existing window by AaronBertrand

Active

Type:	Suggestion
ID:	508776
Opened:	11/6/2009 8:20:38 AM
Access Restriction:	Public

Workaround(s)

view

I don't want to change my default to "results to text", but when I am in a query window where I am using results to text, it is often the case that I will hit "New Query" to spawn a new editor where I am going to perform similar operations. It is very rare that I remember to switch the "results to" setting on the first try. It would be great if the new query window could inherit certain settings when New Query is hit with an existing editor in focus. It already inherits contextual information such as server, login and database... why not some of the editor settings as well?

Details (expand)

English

Tools (SSMS, Agent, Profiler, etc.)

An option that says, "New Query windows inherit properties from window in focus" or something along those lines. Settings I think are useful include the results to mode, include actual execution plan, and any other window-level settings that are *not* default for the window currently in focus. If no window is in focus (e.g. context is on the properties panel, object explorer, etc.) then this setting should be ignored.

Barring an option to set the default behavior, how about an option on the right-click context menu that says, "open a new query editor window with these settings"? This is probably much less work to implement but would still achieve the goal. Added bonus would be a keyboard shortcut to complement Ctrl+N, or at least the ability to set up a custom shortcut that maps to the same behavior.

Faster Development

Improved User Interface

0 attachments

Posted by Dimitri Furman on 11/9/2009 at 12:10 PM

To me, the current behavior of consistently using known and expected settings for all new query windows is preferrable. I'd rather not have to remember the options I might have changed in the current query window, when opening a new one. That said, I wouldn't mind if this were implemented as an optional and non-default configuration setting.

Posted by AaronBertrand on 11/14/2009 at 7:29 AM

Dimitri, I'm not saying it should do this behind your back. I am suggesting that you could set an option to do this, but it wouldn't be set by default. In retrospect, I *prefer* the context menu suggestion, which certainly would not lead to any unexpected behavior.