Post reply

Table statistics and creating new index

  • May 6, 2010 at 7:30 am

    #218646

    I recently had a problem query that on analysis used a poor choice of index- i thought ok, i will create a more suitable non clustered index and problem solved. However when i looked at execution plan again after creating new index, the same old index was being used?

    I would've thought that a new index being created would be sufficient for query engine to take into consideration. I susbsequently ran statistics update with fullscan and finally query used the appropriate new index.

    Am i missing something here?

  • May 6, 2010 at 8:41 am

    #1163273

    depending on the Query structure it may have been running the plan from procedure cache rather than re process the Execution plan.

    Dan

    If only I could snap my figures and have all the correct indexes apear and the buffer clean and.... Start day dream here.

  • May 6, 2010 at 9:23 am

    #1163344

    I might agree with Dan here. Can you drop the plan, or all plans and see if the plan changes? If not, I'd suggest starting a new thread, and posting the DDL and Exec plan.

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

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