Post reply

t-sql key on a table

  • January 7, 2014 at 2:20 pm

    #1678234

    ScottPletcher (1/7/2014)

    Even if some splits do occur, the table won't "easily double in size", since that would require every page to split.

    Automatically adding an identity as the clustering key by default simply is dopey. The clustered index is the most important index on any table, and so it should always be considered carefully.

    You've apparently not experienced the type of massive splitting that I've seen happen. And yes, the clustered index is the most important index on any table and "it should always be considered carefully". That also means not summarily dismissing things like IDENTITY columns. That would truly be a "dopey" thing to do. 😉

    --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