Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Sounds like SQL FTS's ranking is close, but not exactly, what you're looking for, and that you've narrowed down the "not exactly" cases to three:</p> <ul> <li>inflections are ranked identically to non-inflected forms</li> <li>words are ranked identically to their synonyms</li> <li>exact matches (or short titles) are ranked identically as one-word matches within longer titles</li> </ul> <p>What all three of these have in common is that a very simple, automated post-processor on results could use these rules to break ties between identically-ranked results: if there's an exact match, rank it above a non-exact match, and rank shorter titles ahead of longer ones. You may want to consider keeping FTS, and simply putting some code (either in a stored proc or in your app) on top of FTS which sorts groups of tied results by the criteria you mentioned. This would probably be easier than switching to Lucene or another non-Microsoft full-text search implementation.</p> <p>If I were in your shoes, since you've already got something working with FTS, I'd try the post-processing hack above and see if it's "good enough" to meet your needs, since it'd probably be the easiest thing to do. </p> <p>If it's not good enough, I'd start by looking at <a href="http://incubator.apache.org/lucene.net/" rel="nofollow noreferrer">Lucene.NET</a> (free), <a href="http://lucene.apache.org/solr/" rel="nofollow noreferrer">Solr</a> (free), and <a href="http://www.dtsearch.com/" rel="nofollow noreferrer">dtSearch</a> ($$$). Note that none will be as easy as FTS is, though-- especially Lucene.NET which is AFAIK the most popular and is very full-featured but requires a fair amount of coding, configuration, maintenance, etc. You can see <a href="https://stackoverflow.com/questions/120965/which-search-technology-to-use-with-asp-net">this SO thread</a> for some other opinions, there are probabaly more threads like this on SO and elsewhere if you want more opinions. </p> <p>If you're looking for a "did you mean..." spelling-suggestion feature. There's an example of building this kind of feature on top of FTS in <a href="http://books.google.com/books?id=wGwVkAt79bEC&amp;lpg=PT239&amp;ots=fujK826s6e&amp;dq=sql%20server%20fulltext%20spelling%20suggestions&amp;pg=PT253#v=onepage&amp;q=&amp;f=false" rel="nofollow noreferrer">Pro Full-Text Search in SQL Server 2008</a> (link contains some excerpts from Google Books). Would this meet your needs? If not, there are <a href="http://www.google.com/search?hl=en&amp;source=hp&amp;q=spelling+suggestions+in+C%23&amp;aq=f&amp;oq=&amp;aqi=" rel="nofollow noreferrer">lots of other options</a> both free and not. </p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

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