Your machine is probably seriously underpowered for this - however, how many
rows are you returning? You will probably want to limit your results set by
using the ContainsTable or FreeTextTable predicates. You will find that
there is a performance threshold when you return more than 2000 rows. You
will get better performance by limiting the number of rows returned to 200
or so.
--
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 [quoted text, click to view] "Farhan" <Farhan@discussions.microsoft.com> wrote in message
news:55F505A2-C3D6-4E1D-B42E-2A5F75E18B58@microsoft.com...
> hi,
>
> I have response problem with Full Text Index which is 600MB in Size and
> growing incrementally. Previously we had 128MB Ram and 350MB of index size
> then size of index increases to 600MB due to insertion of data after this
> performance degraded so we increased the RAM to 256MB now performance is
> better but the issue is that the database is continuously growing and we
are
> facing the same problem again so tell me I must increase the RAM or is
there
> any remedy for this problem because keep on increasing the RAM is not a
good
> solution.
>
> Kindly help me in this regard how I optimize this, I am using default
> settings of SQL Server.
>
> Configuration:
>
> SQL Server 2000: (Desktop version) with (Service Pack 3a)
>
> Windows 2000: Professional with (service pack 4)
>
> Hard ware configuration: (256 MB Ram, 2.40 GHz, 40GB Hard disk)
>
> Anxiously waiting for reply
>
> Regards
> Farhan Iqbal
>