Re: Treatment of extension column changed in SP4?

Tech-Archive recommends: Fix windows errors by optimizing your registry

Glen,
Interesting... There were significant changes to Full-text Search (FTS) and
the MSSearch components in SP3 (see the below KB articles for public info)
that were carried forward to SP4 that may account for the change in default
behavior that your seeing for your custom .GZ IFilter. One question I have
is what value do you populate the "file extension" column in your FT-enabled
table: ".doc.gz" or ".gz" or ? and what is the datatype of your "file
extension" column? This may be a factor in getting the MSSearch Filter
Daemon (mssdmn.exe) to launch your custom IFilter, although if it worked
pre-SP3, it should of worked post-SP3...

You may want to open a support case with Microsoft PSS SQL Server support as
they have procedures to do extended logging & debugging of the FT Indexing
process that can be used to identify the registry keys/values and .dll's
that are accessed.

Could you also post your FT-enabled table's sp_help output?

Thanks,
John
--
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/


<glenlow@xxxxxxxxxxxxx> wrote in message
news:1129087791.756668.313830@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Hi All
>
> I have several SQL Server 2000 databases that have tables which are
> full-text indexed. In particular I index an image column and specify a
> document type column. This type column often has a compound extension
> like '.doc.gz' and I've written and enabled an IFilter on the box to
> take files ending in .doc.gz etc., decompress it to the original
> extension .doc and call the registered IFilter on .doc.
>
> Up to SP3, everything seems to be hunky-dory and the SQL Server
> dutifully passes the temp file over to my IFilter for indexing. The
> temp files it sees are of the form "abcd..doc.gz"
>
> After SP4 (or some other change I can't determine, although this
> problem has cropped up on a brand new machine with only SQL 2000 SP4 +
> Win2003 Server on it), the temp files are now of the form "abcd.gz" and
> thus my IFilter can no longer figure out the original extension.
>
> Is this a known issue with SP4? Do I need to use "doc.gz" instead of
> ".doc.gz" in the type column? Am I going insane?
>
> Cheers,
> Glen Low, Pixelglow Software
> www.pixelglow.com
>


.

Relevant Pages

  • Re: Treatment of extension column changed in SP4?
    ... Looking for a SQL Server replication book? ... > document type column. ... > extension .doc and call the registered IFilter on .doc. ... > temp files it sees are of the form "abcd..doc.gz" ...
    (microsoft.public.sqlserver.fulltext)
  • Treatment of extension column changed in SP4?
    ... This type column often has a compound extension ... extension .doc and call the registered IFilter on .doc. ... everything seems to be hunky-dory and the SQL Server ... temp files it sees are of the form "abcd..doc.gz" ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Fulltext and text type fields
    ... file system and the ifilter is in the os and SQL is configured to load it), ... and varbinary(with the document type column containing the extension ... Director of Text Mining and Database Strategy ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Word Doc Indexing Problem
    ... datatype which included all those extra spaces! ... This type column can be of any character-based data ... > type and contains the document file extension, ... > varcharcolumn datatype. ...
    (microsoft.public.sqlserver.fulltext)
  • Re: No more indexing on text
    ... of course my type column returns the mime type ... Looking for a SQL Server replication book? ... Looking for a FAQ on Indexing Services/SQL FTS ... Check to make sure that you have an ifilter for each extension listed. ...
    (microsoft.public.sqlserver.fulltext)