>I have been wondering since a while if I have reached a maximum number of records or content to be indexed in the full text indexing on SQL Server. I have SQL Server 2008 R2 on Windows Server 2003. Since a while, the searches take too long. The average was between 2 to 4 seconds before for pretty much that was searched, maybe except for a few very rare exceptions, depending on what the users are entering. However, now, this goes up to 10 to 40 seconds, or even a timeout on SQL Server. This is not acceptable. Recently, I have rebuilt and it did not change anything. I redid the same thing again and it doesn't help.
>
>Any recommendation on what I should do?


mmmmmmemory.....must have more mmmmmmmmmemory...

Seriously, if SQL Server is slowing down my first thought is to add RAM. Also, if you aren't using 64bit, use it (and RAM). Both make serious performance differences. And yes - if that means a new box that handles more RAM, get it.

How big is your database? How many records are in the table you are trying to full text index on? I'm not an expert on the internal limits of SQL Server, but I'd be suprised if you were really hitting limits.