Hi Fabio, Yes, you're on right track.
I'd like to now direct you to first reply from Jack to go through solr tutorial. Even with Solr,, it will take some time to learn various bits and pieces about designing fields, their field types, server configuration, etc. and then tune the results to match the results that you're currently getting from the database. There is lots of info available for Solr on web and do check Lucidworks' Solr Reference Guide. http://docs.lucidworks.com/display/solr/Apache+Solr+Reference+Guide;jsessionid=16ED0DB3B6F6BE8CEC6E6CDB207DBC49 Best of Solr Luck! Sandeep On 2 July 2013 20:47, fabio1605 <fabio.to...@btinternet.com> wrote: > > So, you keep your mssql database, you just don't use it for searches - > that'll relieve some of the load. Searches then all go through SOLR & its > Lucene indexes. If your various tables need SQL joins, you specify those in > the DataImportHandler (DIH) config. That way, when SOLR indexes everything, > it indexes the data the way you want to see it. > > -- SO .... by this you mean we keep mssql as we do!!.... > > But we use the website to run through SOLR.... SOLR will then handle the > indexing and retrieval of data from its own index's, and will make its own > calls to our MSSQL server when required....(i.e updating/adding to > indexs..) > > Am I on the right tracks there now! > > So MSSQL becomes the datastore > SOLR becomes the search engine... > > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Newbie-SolR-Need-advice-tp4074746p4074889.html > Sent from the Solr - User mailing list archive at Nabble.com. >
