sql server full text search: Full text and noise word file -- sql server full text search

Full text and noise word file

Hilary Cotter
7/29/2003 4:32:25 AM

Which noise file did you modify?

The one in %windir%\system32 or the one in c:\mssql7
\ftdata\sqlserver\config?

It should have been the later?

In any event, making such a change should not have caused
this problem, as the indexing processes merely reads the
tables that it is full text indexing.

I suspect there was some other event which caused your
problem.

Is there anything in the event logs that might explain
it? Or the SQL Server error logs?
[quoted text, click to view]

Re: Full text and noise word file

Alex Telford
7/29/2003 4:58:14 AM

The file I modified was the FTDATA one, it was SQL 2K enterprise,
active/passive cluster using a shared disk array. Right after I started
the full text indexing service after editing the files the problem
started. The files I modified became locked, I couldn't even open them
in notepad, error was something like locked by another resource.
Normally you can open them just not save them because they are open by
the search process. Thats when the database went down and wouldn't come
back online, we had to restore from a backup. The fact that my changes
disappeared after I did a failover seems to indicate that the cluster
has master copies somewhere. What I think happened is I restarted the
service which tried to re-read and lock the files, at the same time the
cluster tried to restore the originals and it all got screwed up.
What I hoping for is some documentation on how to modify these files in
a clustered environment.
As for logfiles, I will be looking at them in more detail later but I am
extremely doubtful anything else caused it, there was barely any
connections to the database at that point.

*** Sent via Developersdex http://www.developersdex.com ***

Re: Full text and noise word file

John Kane
7/29/2003 7:37:14 AM

Alex, Hilary,
Restoring your database from backup could be a factor as well and Rene is
correct you must stop the "Microsoft Search" (mssearch.exe) service first
before editing the noise word files, otherwise you are unable to save the
edited noise word files. Also, the frequent SQLServerAgent job that does an
"incremental index on some tables" *might* of also been a factor here and
perhaps should of be disenabled first, then the "Microsoft Search" service
stopped as well.

Regards,
John

[quoted text, click to view]

Re: Full text and noise word file

Alex Telford
7/29/2003 8:12:38 AM

I think the point of my posting is being missed here....

The MSSearch was stopped or I would not have been able to even save my
changes in the first place. The problems started when I started the
service again. I got it to work perfectly in a non-clustered
environment, its when I used the same procedure in a clustered
environment that the problem occured.
Does anyone have any experience, knowledge, links, documentation etc
about modifying these config file in a sql server cluster using a shared
disk?

-Alex

*** Sent via Developersdex http://www.developersdex.com ***

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages in the sql server full text search group.