actual number of rows in exec plan doesn't match real numbers

  • i have a query if i add a condition to the query actual number of rows are tooo high that real number of rows, if i remove the condition it works perfectly fine. i have manually updated the stats for each of these tables, still the same issue?

  • Need to see the sqlplan. Offhand I'd guess there's a spool with multiple executions.


    - Craig Farrell

    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

  • Evil Kraig F (3/21/2013)


    Need to see the sqlplan. Offhand I'd guess there's a spool with multiple executions.

    yup, if i multiple number of executions with actual number of rows it is equal to the number of rows displayed in the exec plan. While i get the exec plan, any thoughts on how to reduce the number of executions?

  • sqldba_newbie (3/22/2013)


    Evil Kraig F (3/21/2013)


    Need to see the sqlplan. Offhand I'd guess there's a spool with multiple executions.

    yup, if i multiple number of executions with actual number of rows it is equal to the number of rows displayed in the exec plan. While i get the exec plan, any thoughts on how to reduce the number of executions?

    Optimize the call to the table below it so it's not joining against the spool... but be aware that's a blind guess without seeing the plan.


    - Craig Farrell

    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 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply