Database Diagrams in Yukon

Ming mentioned this a while back (June 29th) and unfortunately I didn't notice it until now. I've had a few minutes to play with Yukon (SQL Server 2005 for those way behind in the program) and most of that time was spent hunting for the query diagram tools in the new SQL Server UI. But alas, as Ming stated, it isn't there. To quote from Ming's blog: "Database diagram (it was official cut in VS2005, but who knows, we might be asked to put it back.) -- a diagram to lay out the relationship within the database tables/views/".

Well let the guys know then that they have been official asked. I think Paul Murphy may have said it best in Ming's comments: "Someone should be beaten and flogged for cutting database diagrams from the Yukon/Whidbey toolset.”. I could not agree more.

I could come up with a thousand reasons why this shouldn't have been removed, the least of which being the amount of typing the diagram tool saves me. But they all see so painfully obvious that I can't imagine they were not brought up at meetings inside Microsoft. So this leaves me wondering, did they really have a good reason to remove this (puppies in China will die if they built it for example) or did they just have a collective brain fart when this decision was made?

Or maybe I'm wrong and it is there and Ming never said this and this is all a nightmare and I'll soon wake up and have a beer way to early in the morning in order to toast the dream being over…


  • Well it's not really a removal, they just didn't build it into the new .net based management studio. You didn't notice you can't open and edit table contents any more? That's the killer for a lot of folks.

  • I couldn't agree more. I got an answer that some useability test was done that justified a bunch of really bad decisions (IMHO).

    Overall I love 2005, but my two biggest complaints are:

    -No database diagram

    -I loved double click and my data shows up (great for debugging when the bug is data).

    Their statement that the UI people found that people want it to go to the designer may address the majority but when it is a core function for me they really need to address developer as well as DBA needs.


Comments have been disabled for this content.