| John Kane 2005-11-04, 11:43 am |
| Tim,
For those file extensions that you do not want to FT Index, or are not FT
Indexed, you should see the following entry in the application event log for
those file types:
Event Type: SQLFTHNDLR
Event Source: Information
Event Category: None
Event ID: 2001
Date: 8/24/2005
Time: 4:05:35 PM
User: N/A
Computer: JTKWIN2003
Description:
One or more documents stored in image columns with extension 'doc' did not
get full-text indexed because loading the filter failed with error '0x1'.
Replace 'doc' for your file extension. You may also try setting the "file
extension" column value to NULL (if the column is nullable) or to ' '
(space) if it is not, and run a Full Population to compare against your
normal Full Population with this column populated to get some idea of the
performance difference.
Hope that helps!
John
--
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"utcochra" <t.cochrane@inetppc.com> wrote in message
news:1131116166.002651.286560@g14g2000cwa.googlegroups.com...
>I can't find the answer to this anywhere. I have a 16+ Gig table with
> an image column that is full-text indexed based on the usual extension
> column. Some of the extensions are not the standard ones with the
> basic filters. For these extensions I do not want to be indexed with
> the full-text search. How does SQL Server handle these...does it
> ignore them or use the text filter? Could this slow down the
> population of the index if it does not have a filter for that
> extension? Any ideas of how to better manage this are greatly
> appreciated. Thanks!
>
> Tim Cochrane
> t.cochrane@inetppc.com
>
|