SQL Server Performance

index fragmentation: how much is too much?

Discussion in 'SQL Server 2005 Performance Tuning for DBAs' started by bagofbirds, Jan 20, 2010.

  1. bagofbirds New Member

    bagofbirds, Jan 20, 2010
    #2

  2. Luis Martin Moderator

    No it is not bad.
    Lower than 80% could be not good. Lower than 60% is bad.
    Luis Martin, Jan 20, 2010
    #3

  3. FrankKalis Moderator

    Welcome to the forum!
    How many rows & datapages do these tables contain that show over 90% fragmentation?
    FrankKalis, Jan 21, 2010
    #4

  4. preethi Member

    [quote user="Luis Martin"]
    No it is not bad.
    Lower than 80% could be not good. Lower than 60% is bad.
    [/quote]
    Isn't it the other way you want to say? If average fragmentation is less than 20% its good and 20% - 40% not good and >40% is bad?
    Additionally, even if the table is highly fragmented, if the table is not used heavily we don't have to freak out. The size and usage are some factors we need to consider when we think of fragmentation.
    preethi, Jan 21, 2010
    #5

  5. moh_hassan20 New Member

    add to above , don't care for fragmentation for small tables (table with less than 1000 page )
    moh_hassan20, Jan 21, 2010
    #6

  6. Luis Martin Moderator

    [quote user="preethi"]
    [quote user="Luis Martin"]
    No it is not bad.
    Lower than 80% could be not good. Lower than 60% is bad.
    [/quote]
    Isn't it the other way you want to say? If average fragmentation is less than 20% its good and 20% - 40% not good and >40% is bad?
    Additionally, even if the table is highly fragmented, if the table is not used heavily we don't have to freak out. The size and usage are some factors we need to consider when we think of fragmentation.
    [/quote]
    Yes, I don´t know what I was thinking... [:$]
    Apologies.
    Luis Martin, Jan 21, 2010
    #7

Share This Page