Re: Search engine that works with MS SQL Server

Maurício Linhares
Wed, 25 Feb 2009 16:08:30 -0000

And it still is faster at indexing, as it isn''t capable of on-the-fly
updates (if something changes, you´ll have to rebuild your index).

I see Sphinx as an option if your full text search functionality isn''t
that complicated (Sphinx can''t do partial matches or fuzzy search) or
your indexed models don''t change much.

Solr is a full blown full text search tool with most of the features
you''ll see in "enterprise" tools like fuzzy searching (that
enables
things like Google''s "did you mean?" feature), stop words
removal,
faceting and a simple way to write your own customized filters (and
loads of documentations if you need to tweak it).

I tried Ferret and it had loads of problems, specially with concurrent
access, tried Sphinx but the lack of on-the-fly updates, partial
maches (there''s a hack to get this working, but it''s a hack)
and fuzzy
search lead me to try Solr and now I have no reason to look back :)

-
Maurício Linhares
http://alinhavado.wordpress.com/ (pt-br) | http://blog.codevader.com/ (en)



On Wed, Feb 25, 2009 at 12:55 PM, Frederick Cheung
<frederick.cheung-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:
> Last time I looked (admittedly a while back) sphinx was noticeably
> faster at indexing (eg see
http://blog.evanweaver.com/articles/2008/03/17/rails-search-benchmarks
>  and
http://www.mysqlperformanceblog.com/files/presentations/EuroOSCON2006-High-Performance-FullText-Search.pdf
>  ).
>
> As far as the original question goes Sphinx doesn''t have to be
able to
> talk to your database if you can provide a command line tool that will
> produce an appropriately formatted xml stream for sphinx.
>
> Fred