Home Forums SQL Server 2005 SQL Server 2005 Performance Tuning Fill factors, index fragmentation and indexing strategy RE: Fill factors, index fragmentation and indexing strategy

  • October 15, 2008 at 9:48 pm

    #885619

    Matt Miller (10/15/2008)

    Jeff Moden (10/15/2008)

    In that case, I'd use a FILL Factor of 100 for that tiny bit more speed on any SELECTS you may do on the table.

    True - but that assumes a "single load" scenario, where the table is essentially recreated "from scratch" and then left alone afterwards. That also entails dropping the non-clustered's before the truncate and recreating the indexes once the insert has happened. That may well fit your scenario.

    If you plan on leaving the indexes in place (or if the indexes happen over a prolonged stretch of time), you'd still need a fill factor <100.

    No... 🙂 it assumes a clustered PK on the IDENTITY column (like the OP said) which will keep things just as tidy as a single load.

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