"Santo Bartez" <santo71@gmail.com> wrote in message
news:1164749597.924002.302110@n67g2000cwd.googlegroups.com...
> Here's my version of SQL Server 2000 running on Windows Server 2003.
>
> Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
> May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation
> Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
>
> I have a FTI catalog defined on a table with about 2.2 million rows,
> trying to perform a basic CONTAINS query, which has worked perfectly
> for the past 4 weeks until today. It now returns zero rows. The catalog
> shows to have 63877 unique keys.
>
> select mrID, mrGeneration,mrHistory from MASTER1_HISTORY where
> CONTAINS(mrHISTORY, '"2006-11-27" NEAR "juser"') order by
> mrID,mrGeneration
>
> Unfortunately for me, the Administrator chose this morning to empty the
> event viewer without saving the logs, which really really really really
> sucks. :(
>
> Any ideas on how to proceed. I don't want to, if I don't have to,
> perform a complete re-population on this table as it takes several
> hours to finish.
>
> Thanks
> Santo
>

"Santo Bartez" <santo71@gmail.com> wrote in message
news:1164751958.831409.198140@14g2000cws.googlegroups.com...
> Hilary Cotter wrote:
>> Can you check the gatherer logs for information as to what they problem
>> might be? It sounds like possible catalog corruption. You can find the
>> gatherer logs in
>> C:\Program Files\Microsoft SQL Server\MSSQL.X\MSSQL\LOG where X is your
>> intance ID. Your gatherer logs will look like this:
>>
>> SQLFT0013000005.LOG
> I don't seem to have this directory structure. My server is configured
> with SQL Server programs on C: and datafiles on D:\MSSQL
>
> Under C:\PROGRAM FILES\Microsoft SQL Server I have:
> \80
> \MSSQL
> \MSSQL$LOCAL
>
> None of these directories have a MSSQL.#\MSSQL\LOG sub-directory.
>
> Consequently I did find a 'GatherLog' folder on my D: drive in:
> D:\MSSQL\FTDATA\SQLServer\GatherLogs but all these files end in .gthr
> and look to contain hexadecimal values.
>
> Thanks for the reply though, I think I'm going to just re-populate the
> catalog and be done, hopefully it'll not corrupt itself in another 4
> weeks time. :)
>
> -Santo
>

"Santo Bartez" <santo71@gmail.com> wrote in message
news:1164751958.831409.198140@14g2000cws.googlegroups.com...
> Hilary Cotter wrote:
>> Can you check the gatherer logs for information as to what they problem
>> might be? It sounds like possible catalog corruption. You can find the
>> gatherer logs in
>> C:\Program Files\Microsoft SQL Server\MSSQL.X\MSSQL\LOG where X is your
>> intance ID. Your gatherer logs will look like this:
>>
>> SQLFT0013000005.LOG
> I don't seem to have this directory structure. My server is configured
> with SQL Server programs on C: and datafiles on D:\MSSQL
>
> Under C:\PROGRAM FILES\Microsoft SQL Server I have:
> \80
> \MSSQL
> \MSSQL$LOCAL
>
> None of these directories have a MSSQL.#\MSSQL\LOG sub-directory.
>
> Consequently I did find a 'GatherLog' folder on my D: drive in:
> D:\MSSQL\FTDATA\SQLServer\GatherLogs but all these files end in .gthr
> and look to contain hexadecimal values.
>
> Thanks for the reply though, I think I'm going to just re-populate the
> catalog and be done, hopefully it'll not corrupt itself in another 4
> weeks time. :)
>
> -Santo
>