Shouldn't be timeouts in public search anymore except they might be possible when selecting 2007 since the current version of SQL Server has a bug which requires me creating indexes the hard way and I haven't done it for 2007 yet.
The timespan actually has no impact on how long the search takes. Most of the time it takes (it's along the lines of 90%) is strictly a function of how large the underlying search table is.
It's a real brain-dead part of SQL Server that I hope eventually gets fixed. If you want to find all the messages written in March that have the word "moon", it first finds ALL messages containing the word "moon", then narrows it down to March.
It's much better in SQL Server 2005 (our current version) than it was in SQL Server 2000, but it's still brain-dead. And really hurts on systems this large.
News 
Market Data 
Discover 
