June 27, 2012 at 4:08 pm
Is there general guide line on how to reduce number of executions on a portion of query? I will try to post the actual query also.
June 27, 2012 at 5:04 pm
SQL Server Execution Plans By Grant Fritchey
Buy it from Amazon too 😉
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
June 27, 2012 at 5:11 pm
sqldba_newbie (6/27/2012)
Is there general guide line on how to reduce number of executions on a portion of query? I will try to post the actual query also.
I assume you're seeing something along the lines of "Estimated # of rows: 1, # of executions 5 billion" or something equivalent?
It usually comes due to the join type that's being used by the optimizer. You don't typically go after the optimizer at that level, it's too discreet and I think Paul White might be the only person I'm familiar with (outside of Microsoft employees) who has a chance at going after the engine intricacies at that level.
If you're seeing a significant issue with your performance, drop the schema, sqlplan, and query off here and we'll all take a few pokes at it and see what we can find. I wouldn't necessarily go directly after # of executions, though. I'd go after the object(s) at a generic level that's requiring the executions and see what I could alter to allow for a cleaner approach.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply