Fulltext Query Cost

Hi,
I have a query which have fulltext search. The query cost of this query is
around 3-4 only (Show in Execution Plan). I am using ASP calling VBCOM adodb
way to execute this query. Why I always hit timeout for the first search
(using Machine A). There is no timeout after that. Looks like there is some
caching there but bear in mind, I am not searching the same characters after
the first search. Now Machine A don't hit any timeout and then I try Machine
B to search and Machine B hit timeout for the first time now. Any idea?
Thanks,
Kenny
Its hard to say without looking at your query - could you post it here?
I suspect the timeout's are probably caused due to the fact that the catalog
must be read off disk and then for subsequent queries whether they are
different or not, the catalog pages are cached.
You might want to do run a job which warms up the catalogs before searches
hit them.
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?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Kenny" <keejh@.hotmail.com> wrote in message
news:%23Q$ojtU7GHA.1256@.TK2MSFTNGP04.phx.gbl...
> Hi,
> I have a query which have fulltext search. The query cost of this query is
> around 3-4 only (Show in Execution Plan). I am using ASP calling VBCOM
> adodb way to execute this query. Why I always hit timeout for the first
> search (using Machine A). There is no timeout after that. Looks like there
> is some caching there but bear in mind, I am not searching the same
> characters after the first search. Now Machine A don't hit any timeout and
> then I try Machine B to search and Machine B hit timeout for the first
> time now. Any idea?
> Thanks,
> Kenny
>
|||Thank you ... it looks working fine after I rebuild catalog.
Kenny
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23%23w02RV7GHA.3604@.TK2MSFTNGP02.phx.gbl...
> Its hard to say without looking at your query - could you post it here?
> I suspect the timeout's are probably caused due to the fact that the
> catalog must be read off disk and then for subsequent queries whether they
> are different or not, the catalog pages are cached.
> You might want to do run a job which warms up the catalogs before searches
> hit them.
> --
> 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?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Kenny" <keejh@.hotmail.com> wrote in message
> news:%23Q$ojtU7GHA.1256@.TK2MSFTNGP04.phx.gbl...
>