Full-Text Problem
-
Does anyone know why I may be unable to get any results from a full text
query even though my catalog is being populated?
I am running 7.0 SP4 (US English CP 1252) on W2K Advanced SP2 and have
created a test database to demonstrate the problem:
Table "Test" contains:
ID Text
-- -------------------------
1 The cat sat on the mat
2 The cat spat on the mat
ID is the Primary Key and Text is specified for full text searching.
My catalog is populated with 3 items and 30 unique words. I find this
interesting as I only count 7 words including some that would be counted as
noise - perhaps this is a clue. Is there any way of finding out what words
are in the catalog?
when I run:
SELECT *
FROM Test
WHERE CONTAINS(Text, 'cat')
I get 0 row(s) affected. No errors generated in query analyser or the server
event viewer. I have tried many variations on this query without success. A
query using LIKE will work as expected. If I search on a noise word only I
get told that I had only selected noise words so the query is making use of
the full text search routines.
I have disabled and enabled full-text searching, deleted, rebuilt and
repopulated catalogs. I have searched for reports of similar problems
without success.
Does anyone have any ideas?
Thanks.
Paul Murray.
-
Hi Paul,
take a look at this one
http://support.microsoft.com/default.aspx?scid=kb;en-us;241113
Maybe it will help you
Cheers,
Frank
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url] -
quote:
...take a look at this one
http://support.microsoft.com/default.aspx?scid=kb;en-us;241113
...
Thanks Frank but this isn't it. The fields I'm trying to index are VARCHAR(80) or less not huge TEXT fields.
-
quote:
Thanks Frank but this isn't it. The fields I'm trying to index are VARCHAR(80) or less not huge TEXT fields.any reasons why you want to use fulltext search on these fields and not somethink like LIKE ?
Cheers,
Frank
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url] -
Did you remove 'BUILTIN\Administrators' from SQL Server Logins? If you are, you have to grant 'NT Authority\System' to access SQL Server with 'sa' right.
-
quote:
Did you remove 'BUILTIN\Administrators' from SQL Server Logins? If you are, you have to grant 'NT Authority\System' to access SQL Server with 'sa' right.Good point, Allen.
Could definitely cause some headache
Cheers,
Frank
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url] -
Thanks for the help.
I think Allen may have pointed me in the right direction. BUILTIN\Administrators was there but was not set to the default language. I've changed the language back to the default (English from British English) and I now get a series of errors from the Search service and cannot enable FTS on my database!
The errors generated when starting the Search service are:
Event Type:Error
Event Source:Gathering Project Class
Event Category:(3)
Event ID:3006
Description:
The description for Event ID ( 3006 ) in Source ( Gathering Project Class ) cannot be found. Etc.
Event Type:Error
Event Source:Microsoft Search
Event Category:Gatherer
Event ID:3007
Description:
Unable to initialize performance monitoring for the Gatherer Object. The counters are not loaded or the shared memory object can not be opened.
Event Type:Error
Event Source:Microsoft Search
Event Category:Indexer
Event ID:7064
Description:
Unable to initialize performance monitoring for the Indexer Object. The counters are not loaded or the shared memory object can not be opened.
Event Type:Error
Event Source:Gathering Project Class
Event Category:(3)
Event ID:3029
Description:
The description for Event ID ( 3029 ) in Source ( Gathering Project Class ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: MSSearch.Indexer.1, sqlserver SQL0000700005, IDX_E_OBJECT_NOT_FOUND, File or files required for catalog creation were not found.
Event Type:Error
Event Source:Gathering Project Class
Event Category:(3)
Event ID:3028
Description:
The description for Event ID ( 3028 ) in Source ( Gathering Project Class ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: sqlserver SQL0000700005, IDX_E_OBJECT_NOT_FOUND, File or files required for catalog creation were not found..
The Search service then starts.
There seems to be very little information on these errors. It looks to me like I'm looking at a SQL Server reinstall to get past this. Unless anyone has any suggestions.
To answer Frank's question: I am using LIKE at the moment but would just like to be able to offer the flexibility of FTS. E.g. At the moment if my users are searcing for "epson toner" in a description field that is all they will get. The product they want may well be listed as "epson laser toner" or "toner for epson" and will be missed. FTS seemed to be ideal. But I'm beginning to think it's going to be more trouble than it's worth to get it working.
-
Take a look at the Event Veiwer, check if there were any errors in the catalogue build
-
Before I changed the language setting there were no catalog build errors. Now I’m not in a position to do a build (or much else) as FTS is not enabled on the database. I can’t enable it until I solve the above problem. Trying results in the message:
(1 row(s) affected)
Server: Msg 7608, Level 17, State 1, Procedure sp_fulltext_database, Line 49
An unknown full-text failure (80004005) occurred in function CreateCatalog on full-text catalog 'Test'.
Short of reinstalling SQL Server I’m out of ideas.
Viewing 9 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply