I have seen multiple posts that state a where clause can help filter a
full-text search to ensure no full-text records are searched.  What I
understand when showing "set statistics io on" -- the worktable is what the
FTE uses to search for the CONTAINS.  Whether I have a filter (say, on date)
or no filter other than the CONTAINS -- the worktable logical reads are the
same.  I have put a sample query below and the associated reads for
comparison.  Sure, the fullTextTable reads are minimized when there is a date
filter but the FTE worktable remains the same (if some how the filter were
applied to the FTE worktable -- I am assuming the reads would be much lower).

I understand the ContainsTable method is faster, but both are showing the
worktable results to be static whether additional filter criteria added or
not.

Has anyone been able to add filter criteria and see a reduction in the
worktable resources?  

Thanks in advance,
Robert Towne

SELECT message_id, message_date  
into #test
FROM fullTextTable  WITH (NOLOCK)  
WHERE Contains( html_body, 'guarantee')

Table 'Worktable'. Scan count 1, logical reads 7253151, physical reads 5926,
read-ahead reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead
reads 0.
Table fullTextTable  . Scan count 1, logical reads 219502, physical reads
35, read-ahead reads 219461, lob logical reads 0, lob physical reads 0, lob
read-ahead reads 0.

SELECT message_id, message_date  
into #test
FROM fullTextTable  WITH (NOLOCK)  
WHERE Contains( html_body, 'guarantee')
and am.message_date >= 'March  1 2007 12:00AM'  AND  am.message_date <= 'May
10 2007 11:59PM'

Table 'Worktable'. Scan count 1, logical reads 7253151, physical reads 5662,
read-ahead reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead
reads 0.
Table fullTextTable  . Scan count 1, logical reads 50823, physical reads 4,
read-ahead reads 50819, lob logical reads 0, lob physical reads 0, lob
read-ahead reads 0.