Databases
StackOverflow2013
Postsdbo
POImplement Lucene on Existing .NET / SQL Server stack with multiple webservers
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POImplement Lucene on Existing .NET / SQL Server stack with multiple webservers
    text
    copied!<p>I want to look at using Lucene for a fulltext search solution for a site that I currently manage. The site is built entirely on SQL Server 2008 / C# .NET 4 technologies. The data I'm looking to index is actually quite simple, with only a couple of fields per record and only one of those fields actually searchable.</p> <p>It's not clear to me what the best toolset I need to be using is, or what the architecture I should be using is. Specifically:</p> <ol> <li><p>Where should I put the index? I've seen people recommend putting it on the webserver, but that would seem wasteful for a large number of webservers. Surely centralising would be better here?</p></li> <li><p>If the index is centralised, how would I query it, given that it just lives on the filesystem? Will I have to effectively put it on a network share that all the webservers can see?</p></li> <li><p>Are there any pre-existing tools that will incrementally populate a Lucene index on a schedule, pulling the data from an SQL Server database? Would I be better off rolling my own service here?</p></li> <li><p>When I query the index, should I be looking to just pull back a bunch of record id's which I then go back to the DB for the actual record, or should I be aiming to pull everything I need for the search straight out of the index?</p></li> <li><p>Is there value in trying to implement something like Solr in this flavour environment? If so, I'd probably give it it's own *nix VM and run it within Tomcat on that. But I'm not sure what Solr would buy me in this case.</p></li> </ol>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload