>I haven't tested this but I'm actually surprised to hear you say that. I was not impressed by Sql Server's indexed performance of text last time I tried. The biggest issue was how slow and resource intensive the indexing was.

The results were identical when being used on a table which contains about 100,000 records. The index was also good for the creation. But, as you say, once I test it on the one million records table, I'll have more information.

>FWIW, going the Async route does not require a separate machine - you can do it all on a single machine, but of course you'll CPU contention conditions if the lookups are processing intensive. Going to SQL Server helps to offload in this situation, especially if the SQL Server will be primarily used to do the index related data management and not much else.

The search engine is already on a dedicated server. Because of some processes that takes long some time, I wanted to be sure this wouldn't impact the main server.