Re: Full-text catalog is not building properly (completely)

No the catalog should be automatically populated as soon as you create it.
You are looking at the correct log file I think. Sounds like it thinks the
population happened successfully!

--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com

"Greg Smalter" <GregSmalter@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5AE90F70-2733-41F7-9B6B-871B597C7914@xxxxxxxxxxxxxxxx
>I am using the default "Track changes:" option of "Automatic." This should
> prevent the catalog from becoming fully populated to start, though, should
> it?
>
> The platform is Windows Server 2003 Standard x64 Edition with SQL Server
> 2005 Standard x64.
>
> I looked in a file called SQLFT0000500005.LOG and saw no errors. Is there
> more gatherer log information I can get at?
>
> Thank you.
>
> Greg
>
> "Hilary Cotter" wrote:
>
>> I hate to say this to you, but this works for me.
>>
>> There could be a couple of factors involved - you could be using change
>> tracking and the row might not be indexed yet. This is especially the
>> case
>> if you are indexing binary content. I take it you have tried repeatedly
>> and
>> can repro this. Also it could be that for some reason the row was not
>> indexed - check the gatherer logs for any entry.
>>
>> Your noise word list should contain a single space. If it doesn't it will
>> using the Indexing Services noise word lists.
>>
>> One final question - what OS and version of SQL Server and sp?
>>
>> --
>> Hilary Cotter
>> Looking for a SQL Server replication book?
>> http://www.nwsu.com/0974973602.html
>>
>> Looking for a FAQ on Indexing Services/SQL FTS
>> http://www.indexserverfaq.com
>>
>> "Greg Smalter" <GregSmalter@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:0DF7A09B-94DF-4AC9-B6DC-A45738635909@xxxxxxxxxxxxxxxx
>> >I have a full-text index on a Title column in a Books table and I have a
>> > CONTAINSTABLE query that seems to work well in most cases. Recently I
>> > discovered that the query was failing to return an expected result.
>> > When
>> > I
>> > search for titles containing the word "shining," I expect the following
>> > title
>> > to match:
>> >
>> > Stephen King 2 -- Three Volume Boxed Set: Christine; The Shining; Cujo
>> >
>> > But, coming off a fresh rebuild of the catalog (and then waiting until
>> > the
>> > status has gone from Populating to Idle), the above title does not
>> > match.
>> >
>> > The query (which I've simplified) looks similar to this:
>> >
>> > SELECT booksTable.Title FROM Books booksTable
>> > INNER JOIN CONTAINSTABLE( Books, Title, 'shining') titleRank ON
>> > booksTable.BookId = titleRank.[KEY]
>> >
>> > Note that the non-simplified version actually uses the rank information
>> > that
>> > CONTAINSTABLE provides.
>> >
>> > At first, I thought it was a probably with Noise Words or the
>> > semicolons
>> > and
>> > hyphens in that particular title. That's not the case, though. It
>> > turns
>> > out
>> > that if I modify anything about that book whatsoever (say, changing the
>> > word
>> > "Stephen" to "Steven", or even changing a non-Title column in the same
>> > book
>> > row), a subsequent query (the exact same query as above) WILL return
>> > the
>> > result.
>> >
>> > It looks like the full-text catalog is not completely populating
>> > itself,
>> > and
>> > this particular book is only getting added to the catalog when I update
>> > it
>> > in
>> > some way (any way at all). After that, it matches perfectly, just like
>> > I'd
>> > expect.
>> >
>> > My noise words file is completely empty (I tried adding ';' and '-' to
>> > it
>> > and rebuilding, to no effect).
>> >
>> > As I said, I've tried rebuilding the catalog completely and waiting for
>> > it
>> > to repopulate. I need a way to force everything to get indexed right
>> > off
>> > the
>> > bat without waiting for records to be updated before they'll show up in
>> > a
>> > search. How do I do this?
>> >
>> > Thank you.
>>
>>
>>


.

Relevant Pages

  • Re: Full-text catalog is not building properly (completely)
    ... Your noise word list should contain a single space. ... > discovered that the query was failing to return an expected result. ... coming off a fresh rebuild of the catalog (and then waiting until the ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Full text query contained only ignored words
    ... I then created a new catalog on the title column, ... The only other thing in your query that will prevent the row from appearing ... >> Can is a word in the noise word list too. ... >> What you could do is empty the noise word file - leave only a single line ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Full-text catalog is not building properly (completely)
    ... The platform is Windows Server 2003 Standard x64 Edition with SQL Server ... > Your noise word list should contain a single space. ... >> discovered that the query was failing to return an expected result. ... coming off a fresh rebuild of the catalog (and then waiting until the ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Full text search catalog
    ... Search query performance is a function of the total number rows as well as ... > I am using a full-text catalog to perform search inside a 1GB table. ... this was a problem on sql server version 7. ... > says it is able to handle up to 5124 concurrent connections to a fulltext ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Full text search catalog
    ... Search query performance is a function of the total number rows as well as ... > I am using a full-text catalog to perform search inside a 1GB table. ... this was a problem on sql server version 7. ... > says it is able to handle up to 5124 concurrent connections to a fulltext ...
    (microsoft.public.sqlserver.programming)
Loading