2 identical tables reads on Table1 PK is 53394 reads on table2 PK 2246847

  • Tables have identical structure but different indexes (except) PK and different stats.    all DTA recommendations for stats were saved on Table1 all have been deleted on Table 2.  Could these stats be the reason for the difference in logical reads?  Same query executed against both tables.

     

  • Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

  • You've answered you own question.  The tables are, in fact, NOT identical.  You different indexes, which can make the difference between a full table scan (or clustered index scan) and an appropriate seek followed by a solid range scan.  Even if the indexes were identical, is the data?  And, have you checked for page density difference between the two table.  Could one of them be suffering with the problem of "Fast Inserts" where even the insertion of 1 new row can create a whole new, nearly completely empty extent?

     

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

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