Home All Groups Group Topic Archive Search About
Author
28 Dec 2005 5:55 PM
Ed M
Is there a way to remove the database name and ".dbo" from the object name in
the execution plan? I almost never do a cross database join, and all tables
are owned by dbo. Since there is limited room, I'd much rather see the full
table name and index being used. Also, does anyone know why the lines
(representing the flow of data) don't represent the actual size of data
moving around? I'd think that actual rows returned x estimated row size would
determine the thickness of the line, but there doesn't appear to be and rhyme
or reason to the line thickness. It's too bad, since I used to use this
information in SQL 2000 all the time.

Author
28 Dec 2005 8:52 PM
Confused
Don't know about the data size, but regarding dbo issue, check
http://www.aspfaq.com/show.asp?id=2538 (about halfway down the page
under "Always use the dbo. prefix")

If a non-dbo user creates the object without using the dbo prefix,
other users won't be able to see it and more.

I found this out the hard way when my sproc wouldn't run - I had
forgotten the dbo. prefix and it couldn't be found.
Author
28 Dec 2005 9:12 PM
Ed M
Thanks for the reply. I always use dbo. when I create an object. What I am
trying to do is remove this metadata from the graphical execution plan in the
SQL Server 2005 Management Studio. I'd like the 2005 execution plan to
resemble the 2000 execution plan. As far as I'm concerned the 2005 plan
format is a huge step backwards in relation to the 200 plan format.

Show quote
"Confused" wrote:

> Don't know about the data size, but regarding dbo issue, check
> http://www.aspfaq.com/show.asp?id=2538 (about halfway down the page
> under "Always use the dbo. prefix")
>
> If a non-dbo user creates the object without using the dbo prefix,
> other users won't be able to see it and more.
>
> I found this out the hard way when my sproc wouldn't run - I had
> forgotten the dbo. prefix and it couldn't be found.
>
>
Author
28 Dec 2005 9:29 PM
Trey Walpole
I don't believe there is a way to alter the execution plan display.
As for line thickness, i think it's designed just to show relative
result set sizes (e.g., 5M rows or 3M rows will look about the same). i
mean, how would you distinguish between 5M and 3M rows by just the
graphics of a line thickness? it may actually be different, but not that
different to the human eye.

Ed M wrote:
Show quote
> Is there a way to remove the database name and ".dbo" from the object name in
> the execution plan? I almost never do a cross database join, and all tables
> are owned by dbo. Since there is limited room, I'd much rather see the full
> table name and index being used. Also, does anyone know why the lines
> (representing the flow of data) don't represent the actual size of data
> moving around? I'd think that actual rows returned x estimated row size would
> determine the thickness of the line, but there doesn't appear to be and rhyme
> or reason to the line thickness. It's too bad, since I used to use this
> information in SQL 2000 all the time.
Author
28 Dec 2005 9:47 PM
Ed M
Thanks for the reply. I'm hoping someone at Microsoft hears this request for
the ability to customize the data returned and format in the graphical
execution plan.

As far as the thin/fat lines, I'd also like to see someone on the SQL team
explain how they are calculated. I agree with you that it should probably be
a logarithmic representation. The difference between 3 and 5 million isn't as
significant as the difference between 10 rows and 5 million rows. I'd like to
see the line represent the actual not estimated size of the data moved in
megabytes, not rows. I would think this would be more helpful. Hopefully
someone at Microsoft sees this and will give us the option to adjust it.

Show quote
"Trey Walpole" wrote:

> I don't believe there is a way to alter the execution plan display.
> As for line thickness, i think it's designed just to show relative
> result set sizes (e.g., 5M rows or 3M rows will look about the same). i
> mean, how would you distinguish between 5M and 3M rows by just the
> graphics of a line thickness? it may actually be different, but not that
> different to the human eye.
>
Author
29 Dec 2005 9:04 AM
Tibor Karaszi
> Hopefully
> someone at Microsoft sees this and will give us the option to adjust it.

Consider making a request at http://lab.msdn.microsoft.com/productfeedback/

Show quote
"Ed M" <E**@discussions.microsoft.com> wrote in message
news:5A4C9AD4-0B6E-4EF5-A115-D49441AB783A@microsoft.com...
>
> Thanks for the reply. I'm hoping someone at Microsoft hears this request for
> the ability to customize the data returned and format in the graphical
> execution plan.
>
> As far as the thin/fat lines, I'd also like to see someone on the SQL team
> explain how they are calculated. I agree with you that it should probably be
> a logarithmic representation. The difference between 3 and 5 million isn't as
> significant as the difference between 10 rows and 5 million rows. I'd like to
> see the line represent the actual not estimated size of the data moved in
> megabytes, not rows. I would think this would be more helpful. Hopefully
> someone at Microsoft sees this and will give us the option to adjust it.
>
> "Trey Walpole" wrote:
>
>> I don't believe there is a way to alter the execution plan display.
>> As for line thickness, i think it's designed just to show relative
>> result set sizes (e.g., 5M rows or 3M rows will look about the same). i
>> mean, how would you distinguish between 5M and 3M rows by just the
>> graphics of a line thickness? it may actually be different, but not that
>> different to the human eye.
>>

AddThis Social Bookmark Button