July 7, 2011 at 5:04 am
Robert klimes (7/6/2011)
Ninja's_RGR'us (7/5/2011)
Robert klimes (7/5/2011)
not quite sure what you mean by "saved queries"..sql files on the hd.
If this is the case than opening any connection with "Database Engine Query" will result in all .sql files asking for a connection when opening them.
Doesn't work that way. Database Engine Query creates a new query window. It doesn't allow me to browse my file system for previously saved queries.
July 7, 2011 at 7:30 am
Brandie Tarvin (7/7/2011)
Jeffrey, I know I can change connections after bringing things up, but I tend to have so much going on at once that I don't always remember to do that (I usually have multiple copies of SSMS open). Hence the reason I want it to ask me up front.At this point, I'm just going to have to change my SSMS habits.
...And complain to Microsoft for not giving me the option I want. @=)
I also had this challenge (in italics), so I changed to colour coded connections http://sqlfool.com/2009/03/ssms-server-settings/
Red for production, green for development, amber for testing...etc
I also make use of Local Server Groups and Central Management Servers to improve productivity.
________________________________________________________________________________
Can I ask you a rhetorical question...?
________________________________________________________________________________
July 7, 2011 at 8:38 am
Doesn't work that way. Database Engine Query creates a new query window. It doesn't allow me to browse my file system for previously saved queries.
For me it does work that way. After I use "Database Engine Query" once to open a connection then any time I open a file, either by going to File -> Open -> File (ctrl+O) in SSMS or by browsing the File system and double clicking on a .sql file, the connection dialog box appears and I can choose which server I would like to connect to. The only situation that I cannot select server connection is when open a query in a solution or using new query (ctrl+N). This behavior only persists for the current SSMS session.
I have tried this with three different SSMS installation (2008R2 and 2008) and the behavior is consistent.
July 11, 2011 at 5:36 am
Robert klimes (7/7/2011)
Doesn't work that way. Database Engine Query creates a new query window. It doesn't allow me to browse my file system for previously saved queries.
For me it does work that way. After I use "Database Engine Query" once to open a connection then any time I open a file, either by going to File -> Open -> File (ctrl+O) in SSMS or by browsing the File system and double clicking on a .sql file, the connection dialog box appears and I can choose which server I would like to connect to. The only situation that I cannot select server connection is when open a query in a solution or using new query (ctrl+N). This behavior only persists for the current SSMS session.
Ah, see. We're talking about two different things. DEQ only opens up a new query window. Then you're using a completely different method of opening up your saved query files. So saying "use DEQ to open files" is somewhat of a misnomer and explains why it doesn't work for me.
Ctrl-O doesn't open up saved query files for me either, though. It only opens up new query windows.
What are your settings in Tools -> Options that Ctrl-O allows you to browse your file system folders and open up saved queries? Keep in mind that I'm working WITHOUT a solution in SSMS (deliberately so) and will not create a solution to deal with this issue.
July 11, 2011 at 5:49 am
Aha. I've found something interesting.
Your set up must be completely different from mine. The shortcut keys for File -> Open -> File are Ctrl-Shift-Insert (not Ctrl-O) on my version of SSMS. And it does allow me to browse my file system and force a connection each time.
July 11, 2011 at 5:52 am
trevelvis (7/7/2011)
Brandie Tarvin (7/7/2011)
Jeffrey, I know I can change connections after bringing things up, but I tend to have so much going on at once that I don't always remember to do that (I usually have multiple copies of SSMS open). Hence the reason I want it to ask me up front.At this point, I'm just going to have to change my SSMS habits.
...And complain to Microsoft for not giving me the option I want. @=)
I also had this challenge (in italics), so I changed to colour coded connections http://sqlfool.com/2009/03/ssms-server-settings/
Red for production, green for development, amber for testing...etc
And the colors stick after closing and re-opening SSMS. That is AWESOME!
Thanks for the idea. It definitely helps.
July 11, 2011 at 8:21 am
Your set up must be completely different from mine. The shortcut keys for File -> Open -> File are Ctrl-Shift-Insert (not Ctrl-O) on my version of SSMS. And it does allow me to browse my file system and force a connection each time.
You have your keyboard scheme set to SQL Server 2000. Under Tools->options->environment->keyboard.
August 10, 2011 at 4:35 am
This is still bugging me, so I opened up a bug issue on MS Connect. If anyone is interested in voting for it, here it is:
August 10, 2011 at 7:01 am
If you guys still want to keep reading about this, here's a similar thread that's been going since yesteday.
http://www.sqlservercentral.com/Forums/Topic1153598-391-1.aspx
August 10, 2011 at 7:22 am
Thanks, Ninja. Appreciate the link.
August 10, 2011 at 7:28 am
I'm using SQL Server 2008 SP2 (not R2) and the option Jeffrey mentioned, File > Open > File with New Connection is there in SSMS. It allows you to browse for files and prompts for a connection when you open them. Using Tools > Customize you can drag the icon onto the the toolbar.
May 1, 2014 at 9:18 am
Brandie - are you still a dba? lol
Did you EVER get an answer for this? I have same question. I run 2012 ssms blah blah blah.
thanks if you reply. wouldnt be surprised if after all these years you have moved on and are no in this area of technology, or even technology for that matter! 😛
May 1, 2014 at 11:24 am
Royce Blanks (5/1/2014)
Brandie - are you still a dba? lol...
thanks if you reply. wouldnt be surprised if after all these years you have moved on and are no in this area of technology, or even technology for that matter! 😛
I'm curious. Would you have responded to a post this way if I used a gender-neutral or male posting name?
To answer the relevant question "Did you EVER get an answer for this?" Microsoft appears to have fixed it in one of their later service packs, which means my empty environment is opening up correctly now and has been since I updated my client tools. If you're having trouble with SQL 2012 goes, you should post your question in the 2012 forums, not in the 2008 forums.
May 2, 2014 at 6:24 am
Have you looked at using an add-in like SSMSBoost?
May 8, 2014 at 9:17 am
trevelvis (7/7/2011)
I also had this challenge (in italics), so I changed to colour coded connections http://sqlfool.com/2009/03/ssms-server-settings/
Red for production, green for development, amber for testing...etc
I also make use of Local Server Groups and Central Management Servers to improve productivity.
And even the same colour scheme as I use.
It really helps when you are debugging a live issue, developing something else in DEV and promoting another script through the TEST and UAT environments and into LIVE at the same time.
Much easier than repeatedly scrolling so you can check which environment you are connected to and much much much easier than undoing a change which you have just accidently committed to the wrong environment.
Given the chance I'd do the same for the windows backgrounds of the servers.
Viewing 15 posts - 16 through 29 (of 29 total)
You must be logged in to reply to this topic. Login to reply