Introducing The Poorly Designed Management Studio

Since Microsoft has remove the ability for developers to design in
Access through ADPs in SQLS2005, I am going to begin my own discussion
on why the Management Studio is poorly designed for developers. If I
am in error on any of these points, please let me know because it could
greatly improve my shop's productivity.
#1. Let's look a the screen when creating a new table. Now I know
very few screens that are longer than they are wide. As a matter of
fact, I believe the industry is trending toward wide screens. When you
create a new table in Management Studio there are three columns,
"Column Name", "Data Type", and "Allow Nulls." Hmm, OK, three columns.
Let's look at all the wasted space on the screen to the right of the
three columns. Unless you are creating very very very very long column
names, this would be an ideal place to the "Column Properties." But
instead, it's stuck at the bottom, in a very small vertical scroll box
with huge column widths. Nice.
Many more to come...> #1. Let's look a the screen when creating a new table. Now I know
> very few screens that are longer than they are wide. As a matter of
> fact, I believe the industry is trending toward wide screens. When
> you
Real developers know the create table syntax and don't need A GUI. :)
Thank you,
Kent Tegels
DevelopMentor
http://staff.develop.com/ktegels/|||Just reset your video display to 640x480 and you will see that the dialog
fills the screen quite nicely. :-P
"The Cornjerker" <addoty@.gmail.com> wrote in message
news:1142956268.004514.272830@.i39g2000cwa.googlegroups.com...
> Since Microsoft has remove the ability for developers to design in
> Access through ADPs in SQLS2005, I am going to begin my own discussion
> on why the Management Studio is poorly designed for developers. If I
> am in error on any of these points, please let me know because it could
> greatly improve my shop's productivity.
> #1. Let's look a the screen when creating a new table. Now I know
> very few screens that are longer than they are wide. As a matter of
> fact, I believe the industry is trending toward wide screens. When you
> create a new table in Management Studio there are three columns,
> "Column Name", "Data Type", and "Allow Nulls." Hmm, OK, three columns.
> Let's look at all the wasted space on the screen to the right of the
> three columns. Unless you are creating very very very very long column
> names, this would be an ideal place to the "Column Properties." But
> instead, it's stuck at the bottom, in a very small vertical scroll box
> with huge column widths. Nice.
> Many more to come...
>|||#2. Why do all 4 panes default to visible when I create a new view?
Why when I hide the results pane (because I don't need it until I
execute the view) and when I hide the SQL pane (because I'm not a "real
developer") do they re-appear the next time I create a new view? Is
there a setting I'm missing?|||#3. When designing a query and I type in "CASE WHEN fund = '0001' THEN
revenue_jan ELSE 0 END" as a column name I cannot select "Sum" from the
"Group By" drop-down list? I know it works because when I type it in
the SQL pane (like a "real developer") it works and shows up correctly
after I save the view.|||#4. Why can't I export a view or table to Excel?|||Yep, the query window is wide enough. :)
And clicking up a disaster is pretty much out of the question.
ML
http://milambda.blogspot.com/|||Real developers should be submitting schema change requests to the real
DBA(s) -- who also don't need a GUI. :-)

> Real developers know the create table syntax and don't need A GUI. :)|||If you are simply looking to grab the contents of a particular table:
select * from sometable
in the results pane, click the upper left shaded block (this will highlight
the entire result. ctrl+c
open a new xls and select a single cell on the sheet.
ctrl+v
even brings over the column headers (which I don't remember if it did in the
old QA or not).
HTH
--Tony
"The Cornjerker" wrote:

> #4. Why can't I export a view or table to Excel?
>|||I don't think that there is a persisted preference for these. I don't reall
y
use this feature, but after poking around with it a bit, having all the pane
s
there seemed kind of useful given the task at hand. I could also see how
being able to switch this to a tabbed configuration like you can with the
standard query windows might be preferrable.
--Tony
"The Cornjerker" wrote:

> #2. Why do all 4 panes default to visible when I create a new view?
> Why when I hide the results pane (because I don't need it until I
> execute the view) and when I hide the SQL pane (because I'm not a "real
> developer") do they re-appear the next time I create a new view? Is
> there a setting I'm missing?
>