Huge tables with no appropriate column for creating clustered index !

  • steven.malone (12/6/2010)


    Now that the religious(ish) discussion of heap vs. clustered has been resolved let's circle back to the original post.

    IMHO it was a teachable moment for us to reach many newbies on several topics, including the concept of partitioning and covering indexes.

    There is no unique column present in these tables that can be ... can be considered as basis of horizontally partitioning the tables. ...

    Will adding a new unique column (identity column) will help to increase the performance as then these tables could be partitioned ... ? Looking for experts' advice on this.

    I am at work and cannot spend serious time on this beyond the two cents I put in earlier, but are there other threads covering these topics that someone could supply a link to?

    If you look back in this thread, that teaching moment was already answered and tested. 😉

    --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 post 16 (of 15 total)

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