InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSat, 25 May 2013 17:21:40 GMT20http://www.sqlservercentral.com/Forums/Topic1414918-391-1.aspxAside what Gail has said check the index id for the object. If its a heap then it will naturally contain some fragmentation.The page allocation marker is 8 pages, any allocations over that will use uniform extents. This is detailed on msdn, sorry but I don't have link at present.Sun, 03 Feb 2013 05:45:29 GMTPerry Whittlehttp://www.sqlservercentral.com/Forums/Topic1414918-391-1.aspx68 pages is too small to worry about. The usual threshold that's mentioned is 1000 pages. Not a hard and fast number, just a guideSat, 02 Feb 2013 01:39:49 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1414918-391-1.aspxI am defragmenting the database as a maintenance work. But i found that some of the databases avg_fragmentation_in_percent does not reduce.But in some article i have seen that fragmentation on small indexes is often not controllable and The pages of small indexes are stored on mixed extents.So what is the limit for page count for which i can neglect the value of avg_fragmentation_in_percent?In some databases having page count 100 has shown reduce in fragmentation but some db having page count 68 does not reduce fragmentation. So how can i decide for which condition i should consider checking fragmentation?Sat, 02 Feb 2013 01:17:33 GMT IT researcher