1> Maybe, maybe not. mssql text searching is pretty primitive
compared to Solr, just as Solr's db-like operations are
primitive compared to mssql. They address different use-cases.
So, you can store the docs in Solr and not touch your SQL db
at all to return the docs. You can store just the IDs in Solr and
retrieve your docs from the SQL store. You can store just
enough data in Solr to display the results page and when the user
tries to drill down you can go to your SQL database for assembling
the full document. You can..... It all depend on your use case, data
size, all that rot.
Very often, something like the DB is considered the system-of-record
and it's indexed to Solr (See DIH or SolrJ) periodically.
There is no underlying connection between your SQL store and Solr.
You control when data is fetched from SQL and put into Solr. You
control what the search experience is. etc.
2> Not really :(. See:
http://searchhub.org/dev/2012/07/23/sizing-hardware-in-the-abstract-why-we-dont-have-a-definitive-answer/
Best
Erick
On Sat, Jun 1, 2013 at 1:07 PM, Mysurf Mail <stammail...@gmail.com> wrote:
> Hi,
>
> I am just starting to learn about solr.
> I want to test it in my env working with ms sql server.
>
> I have followed the tutorial and imported some rows to the Solr.
> Now I have a few noob question regarding the benefits of implementing Solr
> on a sql environment.
>
> 1. As I understand, When I send a query request over http, I receive a
> result with ID from the Solr system and than I query the full object row
> from the db.
> Is that right?
> Is there a comparison next to ms sql full text search which retrieves the
> full object in the same select?
> Is there a comparison that relates to db/server cluster and multiple
> machines?
> 2. Is there a technic that will assist me to estimate the volume size I
> will need for the indexed data (obviously, based on the indexed data
> properties) ?
