October 15, 2010 at 11:40 am
Hugo Kornelis (10/15/2010)
:laugh: I seem to have built a reputation for myself... :satisfied:I had this one wrong as well. Partially because I don't work with SQL Server 2008 yet (I do have it installed on a laptop, fopr "play" purposes), and partly because I misread the question.
The answer is hidden in the explanation. You can configure different colors for the "query window" (which I knew - that's why I selected "true"), but you cannot configure the colors for "the status bar in SSMS".
This last status bar obviously refers to another status bar than that of the query window. I don't know which status bar, though, and I can't check if it's true. But even if it is, the correct answer should have been "it depends" - since the query window sits within SSMS, you can obviously configure colors for some status bars in SSMS.
Could the author of this question not be referring to the bar at the bottom of the SSMS window that seems to always say "Ready" when I'm in SSMS 2008? Similar to the "status bar" of an explorer window. The color or look of that bar is only changed by the Windows display properties appearance settings. [see attachment]
I believe Microsoft has started re-using terms for different applications. If the "status bar" references the bar at the bottom of a query window or Object explorer, then what is the bar at the very bottom of SSSM called now:-D?
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
October 15, 2010 at 12:12 pm
I have awarded back all points and edited the question to include the answer for future people.
Not a great question, and my apologies.
October 15, 2010 at 3:05 pm
William Vach (10/15/2010)
Thanks for the information. I was not aware that you could also set the query window color through the connection dialogue box. I did discover a quirk when using that method. It looks like the color is associated with the instance entry in the drop down. If you are connected to an instance and then change to another instance that you manually key in, the status bar will retain the color of the instance that you were originally connected to and also change the color of the manually keyed in instance when you subsequently select it from the drop down.This QOD sure brought out a lot of discussion about a little known but useful feathre of SSMS.
Yes, it is associated with the instance. It works this way for both connections set up in your registered servers, and for when changing connections or selecting "Connect" in the object explorer.
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
October 15, 2010 at 3:06 pm
Steve Jones - SSC Editor (10/15/2010)
I have awarded back all points and edited the question to include the answer for future people.Not a great question, and my apologies.
I don't think I've ever seen any other question where the editor has put what the answer is in the question before...
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
October 15, 2010 at 3:41 pm
WayneS (10/15/2010)
Steve Jones - SSC Editor (10/15/2010)
I have awarded back all points and edited the question to include the answer for future people.Not a great question, and my apologies.
I don't think I've ever seen any other question where the editor has put what the answer is in the question before...
I have a few times in the past when I couldn't come up with a good way to reword the question
October 15, 2010 at 4:47 pm
Intriguing question.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
October 15, 2010 at 10:45 pm
Interesting question, but even better discussion. Thanks all!
October 19, 2010 at 1:22 am
I would have thought that Ans is true because we can specify color in connection properties
October 19, 2010 at 1:25 am
DhruvShah (10/19/2010)
I would have thought that Ans is true because we can specify color in connection properties
Well, if you read the editor's comments at the question and this thread, you'll know the answer.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
October 22, 2010 at 6:29 am
Spooky - I have also decided to use a horrible pink for production!
January 17, 2012 at 10:14 am
I know that this is an old thread, but I think it's the best place...
I've just been caught out by this - luckily nothing major, but still a production server issue.
I had my QA server set to blue and production set to red in my Registered Servers list, but, for this little-used server, I had got a different setting under File/Connect Object Explorer/Options and this is the colour that seems to take priority when using the 'Connect' button in Object Explorer.
I then managed to execute some QA code on production and stuff up an important SQL Agent job, which we rapidly unstuffed:-)
Does anyone know where these settings are held? I'd like to remove anything that might override what I have set up under Registered Servers.
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
January 17, 2012 at 10:31 am
Phil take a look at Wayne's post on page 1 of this thread. http://www.sqlservercentral.com/Forums/Topic1004880-2739-1.aspx He explains how the color can be set from two locations depending on how you connect. Sounds like you were a victim of using the Object Explorer to connect. Seems like MS should fix that.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
January 17, 2012 at 11:05 am
Hi Sean and thanks for the response.
My point is that using Object Explorer to connect works as you would expect (with colour coding from Registered Servers) unless that colour coding has been overridden, as mentioned in my earlier post.
So my thinking was that all would be well if I could remove all of the Object Explorer colour settings somehow. I could of course do this manually, but would rather just excise a few Registry keys (if that is where the settings reside) to do the job properly.
Thanks
Phil
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
January 17, 2012 at 12:06 pm
Ahh I see where you are going. I wish I knew where that info was stored. You are probably correct that it is in the registry somewhere...
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
Viewing 14 posts - 31 through 43 (of 43 total)
You must be logged in to reply to this topic. Login to reply