"Franky" <Franky@discussions.microsoft.com> wrote in message
news:05282548-CE54-4E6E-8AD2-E0A58DDA9653@microsoft.com...
> We are using FTS on a table which has for the moment 4500 rows.
> When we restart the FTS-service, or no one uses the search for a while,
> then
> the first FTS-query takes up to 60 seconds. (also when there is only 1
> record
> returned)
> While lookalike queries after the first take about 60 miliseconds.
> We've alreade rebuild the catalog, but this does not help.
>
> The problem is on the FTS. The query I use to test the performance uses
> only
> the FTS-engine, see statement below.
> select [KEY] from containstable(EURO.TB_ProductGroup_FTS_V2,*,'test')
>
> Does anyone know how to fix that ?

"Hilary Cotter" wrote:

> This is because the full-text engine relies on the file system cache to keep
> the catalogs in cache. If they are not used they are flushed to disk. You
> need a sql server job that runs ever 5 minutes or so to search on something
> relatively large - like the word the.
>
> --
> RelevantNoise.com - dedicated to mining blogs for business intelligence.
>
> 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
> "Franky" <Franky@discussions.microsoft.com> wrote in message
> news:05282548-CE54-4E6E-8AD2-E0A58DDA9653@microsoft.com...
> > We are using FTS on a table which has for the moment 4500 rows.
> > When we restart the FTS-service, or no one uses the search for a while,
> > then
> > the first FTS-query takes up to 60 seconds. (also when there is only 1
> > record
> > returned)
> > While lookalike queries after the first take about 60 miliseconds.
> > We've alreade rebuild the catalog, but this does not help.
> >
> > The problem is on the FTS. The query I use to test the performance uses
> > only
> > the FTS-engine, see statement below.
> > select [KEY] from containstable(EURO.TB_ProductGroup_FTS_V2,*,'test')
> >
> > Does anyone know how to fix that ?
>
>