title: What's the best approach for using SOLR with web projects?
body: <p>ok, I'm totally new to SOLR and Lucene, but have got Solr running out-of-the-box under Tomcat 6.x and have just gone over some of the basic Wiki entries.</p>
  
  <p>I have a few questions, and require some suggestions too.</p>
  
  <ol>
  <li><p>Solr can index data in files (XML, CSV) and it can also index DBs. Can you also just point it to a URI/domain, and have it index a website in the way google would?</p></li>
  <li><p>If I have a website with "Pages" data, so "Page Name", "Page Content" etc, and "Products Data", so "Product Name", "SKU" etc, do I need two different Schema.xml files? and if so, does that mean two different instances of Solr?</p></li>
  </ol>
  
  <p>Finally, if you have a project with a large relational and normalized database, what would you say is the best approach from the 3 options below?:</p>
  
  <ol>
  <li><p>Have a middleware service running in the background, which mines the DB and manually creates the relevant XML files to then send to SOLR</p></li>
  <li><p>Have SOLR index the DB directly. In this case, would it be best to just point SOLR to views, which would abstract all the table relationships?</p></li>
  <li><p>Any other options I'm unaware of?</p></li>
  </ol>
  
  <p>Context: We're running in a Windows 2003 environment, .NET 3.5, SQLServer 2005/2008</p>
  
  <p>cheers!</p>