hi i had defragmented the SP datebase a week back and just checked, 38 tables are fragmented and most of them are more then 80 percent fragmented. as DB is using more frequently by a larg no of users but just want to know what should be the plan to tackle this as site is running slow? any comments/suggestions are welcome; regards

Hi, Automate a schedule of volume and Db defrag... The following are related to file fragmentation only 1. Logical units should be large enough to contain the data that will be stored plus at least 25%. This is to allow for enough space for a defragmentation routine to optimize file structures. 50% may be a safer recommendation as there are always storage requirements that aren’t thought of in the beginning. 2. Set Fill Factor to 70 to reduce fragmention: Fill factor can be used to further improve index data storage and performance. When indexes are created or rebuilt, the fill factor value (1-100) determines the percentage of space on each leaf level page that can be filled with data. The remaining space is reserved for future growth. For many situations the default server-wide fill factor level of 0 is optimal; however, for Microsoft Office SharePoint Server 2007, a server-wide setting of 70 is optimal to support growth and minimize fragmentation. 3. To combat fragmentation in SharePoint databases, Microsoft released KB article 943345. The stored procedure provided by this KB article provides a no-nonsense approach to database maintenance. You dont have to know a whole lot other than to just run the stored proc against your SharePoint databases regularly. Routine database maintenance is essential for the smooth operation of Microsoft SharePoint Products and Technologies databases -IvanIvan Sanders My LinkedIn Profile, My Blog, @iasanders.