Index Seek on Non Clustered Index cost is very high (92%) how to reduce this ?

  • Hi ALl,

    Please give your suggestions to resolve this problem.

    Index Seek on Non Clustered Index cost is very high (92%) how to reduce this ?

  • No way to answer with that limited information. Please at least post the execution plan.

    First though, is that a problem? The costs have to add to 100% across the plan, so is that seek problematic? Is the query even problematic?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Add an unnecessary sort.

    That should make the index seek use proportionately less cost of the entire query.

    But, why would you want to?

    Catch-all queries done right [/url]
    Gail Shaw's Performance Blog[/url]

  • kbhanu15 (7/14/2014)


    Hi ALl,

    Please give your suggestions to resolve this problem.

    Index Seek on Non Clustered Index cost is very high (92%) how to reduce this ?

    I've run into this in the past. Like Gail says, not enough information to call out a fix but, if it were me, I'd check the properties of the Index Seek in the execution plan and see how many times it's executing. If it's doing 1 seek per row instead of a single seek and a range scan, that could be one of the problems.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

Viewing 4 posts - 1 through 3 (of 3 total)

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