As a rule of thumb if the fragments are higher than 30 then you should be looking at re-indexing (REORGANIZE). Simply run the script to see if any of your fulltext indexes require any action.
SELECT OBJECT_NAME([table_id]) AS TableName, COUNT([fragment_id]) AS Fragments FROM sys.fulltext_index_fragments GROUP BY OBJECT_NAME([table_id]) HAVING COUNT([fragment_id]) >=30
This article describes how an index gets fragmented and the steps which a DBA can take to fix index fragmentation
2008-12-11
2,876 reads
Script to list out all fragmented indexes for a given database, with options to only view them, reorganize them, or rebuild them in one fell swoop.
2012-05-25 (first published: 2012-05-15)
3,077 reads
This article decribes how defragementing a 900 GB drive assisted in addressing major performance issues on a reporting server.
2012-04-20
6,526 reads
If you are relying on using 'best-practice' percentage-based thresholds when you are creating an index maintenance plan for a SQL Server that checks the fragmentation in your pages, you may miss occasional 'edge' conditions on larger tables that will cause severe degradation in performance. It is worth being aware of patterns of data access in particular tables when judging the best threshold figure to use.
2012-03-14
3,229 reads
Just a stab at automating index maintainenance in SQL Server 2008
2013-01-11 (first published: 2008-11-07)
2,701 reads
