So I’m loving the ability to configure what information I want to see in my object explorer details window (SQL Server 2008). In SSMS if you don’t have your object explorer details window up hit F7. Now click on the Databases folder.
So by default (at least on my installation) you’ll see
DatabaseName
PolicyHealthState
RecoveryModel
CompatibilityMode
Collation
Owner
Definitely alot more useful information than what was provided in SSMS 2005 but wait… right click on the column bar and you now see a huge list of options of things you’d like to see in your object explorer details window. Some environments don’t use different collations so that might be taking up valuable real estate on your window so you can deselect it to remove it and add some other columns that you might find useful (Size MB? Last Backup date? Mirroring Status?)
The same ability to customize your object explorer details is available for the subfolders as well (Tables, Views, Stored Procedures, etc)
Anyways this is just another small but nice improvement in SQL Server 2008. Happy Monday!!
Enjoy
Golly…. I absolutely HATE 2008 with a passion because of the changes it’s made to object explorer. On in particular is this “object explorer details” concept. I’m in an medium sized database with Several hundred procedures. However… in order to see those procedures it would seem so far that I have to open this “object explorer details page”. So… now I’ve got 10+ query pages open. I want to go check out the details of a table and open an SP. In 2005 this was so simple. It was effortless. In 2008 I have to play with tabs or do all sorts of weird stuff. It’s aggravating. The information is organized poorly and is very unhelpful. If they were going to make it configurable, they should have made it configurable to the point that it would mirror 2005. Far better organization there. But that’s just my opinion.
-5 stars out of 5 for 2008 in my book. I’ve had nothing but trouble with it. Installing, utilizing, and so forth. It’s default settings aren’t even intelligent or useful. You have to go and reconfigure the entire thing before you can utilize it with a medium or larger database. It’s like it’s default setup for small databases or something. I mean, sure, no matter what you’ll likely have to reconfigure something. But some of the default settings blocked remote login to my database…. huh? Any respectable sized database is going to be remote… The state of those default setting is silly stupid in my opinion.