full-text : first request is very slow

full-text : first request is very slow

Post by Noro » Fri, 19 May 2006 01:20:42


I develop an ASP.NET application which is connected to SQL 2005.

I encounter a problem, it is that always the first request that I sending on
fields contained in a full-text index is extremely slow and always exceed
the 30 seconds; the requests which follow are very fast (1 second).

Requests which do not use full-text index are fast as of first request.

I could not detect the source of the problem; if somebody has an idea or
already encountered this problem!

Thank you in advance


full-text : first request is very slow

Post by Noro » Fri, 19 May 2006 04:50:02

Hi Hilary,

Thank you for your answer.

On my Test Server, I have 1Go RAM and during my tests I checked that there
were only 300 to 350 Mo used. However I have always the same problem with
the first request with each restarting of SQL Server or after certain
duration of inaccessibility to the DB.

Is there an option for charging the full text catalog in RAM with the
starting of SQL so that it is ready as of the first request?

Any idea?



full-text : first request is very slow

Post by Hilary Cot » Fri, 19 May 2006 20:39:47

AFAIK - No, but you might want to set resource_usage to 5
(sp_fulltext_Service 'resource_usage',5).

You could also have a job run on startup which will issue a full-text query.

Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

Looking for a SQL Server replication book?

Looking for a FAQ on Indexing Services/SQL FTS

full-text : first request is very slow

Post by Noro » Tue, 23 May 2006 18:46:29

hanks for your help.

I planned a work which starts each 10 minutes and contains a full-text
request. Now my first request is fast.


"Hilary Cotter" < XXXX@XXXXX.COM > a rit dans le message de news:


full-text : first request is very slow

Post by Dave Pool » Sun, 28 May 2006 04:52:30

he reason for this could be because your system does not have access to the
internet. On loading of wordbreakers/filters the mssearch process will try
to validate the signature, it then tries to check for signature revokation
which involves checking a service on the internet. This has a timeout
(about 45 seconds I believe). Once the dll is loaded it will not check

This could be why you see the large response time the first time you issue a

If no queries run for some time (I think it is 30 minutes) the resources
will be unloaded to save memory, next time a query comes along it will need
to go through the validation phase again.

Your task running a fulltext query every 10 minutes should get around this

Dave Poole
SQL Server Fulltext Team

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at

"Noro" < XXXX@XXXXX.COM > wrote in message
news: XXXX@XXXXX.COM ...