SQL Server Home
Huge Operator cost in Estimated execution plan
as Won't Fix
4/29/2009 2:08:16 PM
Primary Feedback Item:
User(s) can reproduce this bug
While testing the performance of large queries (due to lack of production size copies), Estimated execution plan is used. But the operator costs are being showed incorrectly from the estimated execution plan for certain TSQL constructs even if the stats are upto date. It helps if this issue is corrected.
Here is some notes on this issue.
Upon feedabck from Erland, moving to tools from SQL Engine.
SQL Server 2005 - Enterprise Edition
Tools (SSMS, Agent, Profiler, etc.)
Win2003 Enterprise Server (SP2)
Operating System Language
Steps to Reproduce
if exists(select 1 from dbo.TableA where col1 >3200000 and col1 <4000000)
delete from dbo.TableA where col1 >3200000 and col1 <4000000
Estimated operator is in miilions (427095307 %)
Should be reasonable within 100%
to post a comment.
Please enter a comment.
on 3/30/2010 at 10:40 PM
Thank you for reporting the problem via connect. I apologize for the delay in responding to this.
There is a similar bug that we are tracking for this issue - http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=370798 which we are considering for the future release. Given this, I am going to resolve your issue as duplicate of the other issue. In case you have any question or comments then contact me directly at firstname.lastname@example.org
on 5/18/2009 at 2:55 PM
Thank you for the feedback! If I understand you correctly, the issue you are reporting is related to how Management Studio reports percentages of the operator cost in the batch. In this particular case, the percent cost of the statements in the THEN-part is computed relative to the cost of the query in the IF-part of the statement which may be completely unrelated.
Until this is fixed, the workaround obviously is to ignore the percentage but look at the estimated value itself. The estimated values can be observed for each operator by holding mouse pointer over a particular node (or by looking at the node properties – default shortcut is F4).
SQL Server Engine
on 4/30/2009 at 7:18 AM
Oh, come on, what's a few million percent among friends??!
to post a workaround.
Please enter a workaround.
© 2014 Microsoft