Rank cost of graphical execution plan components in SSMS
When a large execution plan is generated, it can be tedious and time consuming to find the highest-cost operations to performance-tune.
Upvotes: 19<=-=Jul 27 2009 5:33AM=-=>
Even a visual cue, such as a red background or outline, would be useful. Then if you have a large plan and you zoom out to see it all, you can see the high cost items instantly.<=-=Aug 2 2009 8:36PM=-=>
I’d also like to see something like “Operator Cost 1% SubTree Cost 84%”, so that I can more easily track down the tree. Previously I was having to do this using the text-based plan and Excel… (!!!!)<=-=Jan 19 2010 3:11PM=-=>
I concur with both Aaron and Rob. When dealing with large stored procedures, it can be almost impossible to effectively use the graphical query execution plan. Some way of navigating, sorting, or visually identifying the plan by expense would be very useful.<=-=Jan 19 2010 3:17PM=-=>
The best suggestions are obvious when you see them. This is one of those. Can’t describe how much time I’ve spent looking through plans for high cost operations. I normally search the XML instead. That’s ridiculous.<=-=Jan 22 2010 1:25PM=-=>
This is a good idea that would it much easier to read graphical execution plans (which are very often used by many DBAs).<=-=Jan 26 2010 9:33PM=-=>
Thank you for this valuable feedback. This is indeed a low effort/high impact feature.
We will put forth the DCR along with the rest being considered for the next release, and then accordingly prioritize it. Will keep this thread updated on the progress.
Dev Lead, SDM DEV.
Just circled back to this item. SQL Sentry recently released a free tool called Plan Explorer which overcomes many of the limitations we find in SSMS plans, and shows a lot more detail as well:
Hi!, thanks for writing in to Microsoft.
We recently took a look at this feature request again and triaged it against several others and unfortunately, it did not meet the bar to be fixed. While we are closing this request as ’won’t fix’, we have taken note of this internally and we will try & incorporate this request when we revisit this functionality in a future release of SSMS.
Sanjay Nagamangalam, SQL Server Manageability