>For processes that could possibly timeout it's best to move those off to an asynchronous process. WWWC comes with a class for doing just that--lookup the wwAsyncWebRequest class in the help file. If you have the WebRAD book, there's also a clear example of how an async request works.

I've been thinking about that approach. However, with a better infrastructure, I need to get those results immediately. So, I'll probably give a try with SQL Server for the search engine as I could use the builtin mechanisms. If it doesn't have any bug with large table being indexed, then that could resolve the issue.